all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: emacs-orgmode@gnu.org
Subject: Re: Suggestion org-lint - Duplicate NAME
Date: Sat, 24 Oct 2015 13:18:15 +0200	[thread overview]
Message-ID: <m2vb9w7bwo.fsf@krugs.de> (raw)
In-Reply-To: <87eggky522.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 24 Oct 2015 11:44:05 +0200")

[-- Attachment #1: Type: text/plain, Size: 2758 bytes --]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> 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.

Thanks - that is probably better.

Rainer


>
> Regards,

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug

PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

      reply	other threads:[~2015-10-24 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 11:35 Suggestion org-lint - Duplicate NAME Rainer M Krug
2015-10-24  9:44 ` Nicolas Goaziou
2015-10-24 11:18   ` Rainer M Krug [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2vb9w7bwo.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.