From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Suggestion org-lint - Duplicate NAME
Date: Sat, 24 Oct 2015 11:44:05 +0200
Message-ID: <87eggky522.fsf@nicolasgoaziou.fr>
References: <m2oafrb0fx.fsf@krugs.de>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55942)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1ZpvLZ-0002xJ-G8
	for emacs-orgmode@gnu.org; Sat, 24 Oct 2015 05:42:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1ZpvLY-0006Sc-Cw
	for emacs-orgmode@gnu.org; Sat, 24 Oct 2015 05:42:45 -0400
Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:50132)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1ZpvLY-0006SY-62
	for emacs-orgmode@gnu.org; Sat, 24 Oct 2015 05:42:44 -0400
In-Reply-To: <m2oafrb0fx.fsf@krugs.de> (Rainer M. Krug's message of "Thu, 22
	Oct 2015 13:35:30 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org

Hello,

Rainer M Krug <Rainer@krugs.de> writes:

> I have a long org document in which I copied around some analysis blocks
> to do the same analysis (and format of results) for different simulation
> parameter combinations.
>
> But sometimes I forget to change the #+NAME: properties.
>
> org-lint is a gret help in finding these, but as my names are long and
> cryptic, it is not easy to see where the duplicates are. An example:
>
> ,----
> |   2442 high  Duplicate NAME "fig_fitEachExamplesOptimMahat"
> |   2447 high  Duplicate NAME "fig:fitEachExamplesOptimMahat"
> |   2451 high  Duplicate NAME "fig_fitEachExamplesUAOptimMahat"
> |   2456 high  Duplicate NAME "fig:fitEachExamplesUAOptimMahat"
> |   2480 high  Duplicate NAME "fig_fitEachExamplesOptimMahat"
> |   2487 high  Duplicate NAME "fig:fitEachExamplesOptimMahat"
> |   2491 high  Duplicate NAME "fig_fitEachExamplesUAOptimMahat"
> |   2498 high  Duplicate NAME "fig:fitEachExamplesUAOptimMahat"
> `----
>
> was the output of the linting. Now it took me quite a few attempts
> (which were aborted by ignoring the problem) to see which ones are
> duplicates. It would be easier, if, in the case of duplicates, the
> entries could look as follow:
>
> ,----
> |   2442 high  Duplicate (2442, 2480) NAME "fig_fitEachExamplesOptimMahat"
> |   2447 high  Duplicate (2447, 2487) NAME "fig:fitEachExamplesOptimMahat"
> |   2451 high  Duplicate (2451, 2491) NAME "fig_fitEachExamplesUAOptimMahat"
> |   2456 high  Duplicate (2456, 2498) NAME "fig:fitEachExamplesUAOptimMahat"
> |   2480 high  Duplicate (2442, 2480) NAME "fig_fitEachExamplesOptimMahat"
> |   2487 high  Duplicate (2447, 2487) NAME "fig:fitEachExamplesOptimMahat"
> |   2491 high  Duplicate (2451, 2491) NAME "fig_fitEachExamplesUAOptimMahat"
> |   2498 high  Duplicate (2456, 2498) NAME "fig:fitEachExamplesUAOptimMahat"
> `----
>
> This would make it easier to find the duplicates, especially if they are
> not in adjacent messages.

It could potentially create very long, i.e., unreadable, warning
messages. Instead, you can now sort warning messages, which helps
putting together duplicate names.

Regards,

-- 
Nicolas Goaziou