From: Samuel Wales <firstname.lastname@example.org> To: email@example.com 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 targets. so i am curious what the purpose of the default is? On 5/20/21, Jean Louis <firstname.lastname@example.org> wrote: > * Nicolas Goaziou <email@example.com> [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. https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
next prev parent 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 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: 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='CAJcAo8uXh+g+=T4RVPTEuCXsq6rv+Jfqs8rqz8JfpCsXfrJn+Q@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Custom <<anchor>> possibility?' \ /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
Code repositories for project(s) associated with this 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).