From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Suggestion org-lint - Duplicate NAME
Date: Sat, 24 Oct 2015 11:44:05 +0200 [thread overview]
Message-ID: <87eggky522.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2oafrb0fx.fsf@krugs.de> (Rainer M. Krug's message of "Thu, 22 Oct 2015 13:35:30 +0200")
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
next prev parent reply other threads:[~2015-10-24 9:42 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 [this message]
2015-10-24 11:18 ` Rainer M Krug
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eggky522.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).