From: Nicolas Goaziou <firstname.lastname@example.org> To: Spencer Baugh <email@example.com> Cc: firstname.lastname@example.org Subject: Re: HTML export uses anchor ids which change on every export Date: Wed, 09 Jun 2021 14:19:00 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Spencer Baugh's message of "Tue, 08 Jun 2021 19:31:55 -0400") Hello, Spencer Baugh <email@example.com> writes: > Nicolas Goaziou <firstname.lastname@example.org> writes: >> No, for public links, CUSTOM_ID is the only sane way to handle this. >> Even "sec-2" could betray you if you slightly modify the document. > > I understand and agree. However, "sec-2" is strictly better than the > current situation in terms of link stability: There are many document > modifications that don't change "sec-2", and there are no document > modifications that don't change the current id format. > > If some user likes link stability a litle bit, but not enough to add > CUSTOM_ID to every single heading, then providing some option to > generate ids like "sec-2", which are stable in some situations for very > little cost, is good for that user. I disagree. "sec-2" is not "strictly better". Actually, long ago, Org used "sec-2", or "outline-2", but we got bug reports about that (in particular, it broke publishing) too. A weaker poison is no healthier. Please note that, if you're exporting again and again the same document, you ought to publish it, in which case referenced links are stable. Also, not too long ago, Timothy had a different suggestion for the internal link stability problem. One idea to move forward could be to provide a defcustom to let users use whatever function they want to generate internal links. I think, however, it might be tricky to have that function handle properly duplicates. Regards, -- Nicolas Goaziou
prev parent reply other threads:[~2021-06-09 12:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-29 18:18 sbaugh 2021-05-29 19:50 ` Nicolas Goaziou 2021-05-29 19:54 ` Timothy 2021-05-29 23:10 ` Tim Cross 2021-05-30 5:16 ` Timothy 2021-05-30 6:56 ` Tim Cross 2021-05-30 12:11 ` Nicolas Goaziou 2021-06-08 23:31 ` Spencer Baugh 2021-06-09 12:19 ` Nicolas Goaziou [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 List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: HTML export uses anchor ids which change on every export' \ /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).