emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Custom <<anchor>> possibility?
Date: Thu, 20 May 2021 15:18:57 -0700	[thread overview]
Message-ID: <CAJcAo8uXh+g+=T4RVPTEuCXsq6rv+Jfqs8rqz8JfpCsXfrJn+Q@mail.gmail.com> (raw)
In-Reply-To: <YKbEWGaEJYE48Kva@protected.localdomain>

thanks for pointing us to this variable.

docstring says "This process ensures that these values are unique and
valid...", so it sounds like you could create non-unique or invalid
identifiers without it.

does this mean, for example, if the user exports a subtree with two
link targets with the same user label, then if this variable is
non-nil, then the output could include more than one link target?

what if this var were nil [the default], my brain is not working well
now, but it seems as if the exporter could still get confused which
target to link to, even if it is not printing duplicatedly-named

so i am curious what the purpose of the default is?

On 5/20/21, Jean Louis <bugs@gnu.support> wrote:
> * Nicolas Goaziou <mail@nicolasgoaziou.fr> [2021-05-20 23:00]:
>> > Is there a possibility to tell Org, that <<target>> really remains
>> > "target" as in id="target" instead of a random ID?
>> See `org-html-prefer-user-labels'.
> Thanks.
> --
> Jean
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
> Sign an open letter in support of Richard M. Stallman
> https://stallmansupport.org/
> https://rms-support-letter.github.io/

The Kafka Pandemic

Please learn what misopathy is.

  reply	other threads:[~2021-05-20 22:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 19:25 Custom <<anchor>> possibility? Jean Louis
2021-05-20 19:59 ` Nicolas Goaziou
2021-05-20 20:19   ` Jean Louis
2021-05-20 22:18     ` Samuel Wales [this message]
2021-05-20 23:00       ` Jean Louis
2021-05-20 23:50         ` Samuel Wales
2021-05-21 12:51       ` Nicolas Goaziou
2021-05-21 19:28         ` Samuel Wales

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:

  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='CAJcAo8uXh+g+=T4RVPTEuCXsq6rv+Jfqs8rqz8JfpCsXfrJn+Q@mail.gmail.com' \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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