From: Tim Cross <theophilusx@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: HTML export uses anchor ids which change on every export
Date: Sun, 30 May 2021 16:56:22 +1000 [thread overview]
Message-ID: <87r1ho8z6f.fsf@gmail.com> (raw)
In-Reply-To: <87wnrgls2y.fsf@gmail.com>
Timothy <tecosaur@gmail.com> writes:
> Tim Cross <theophilusx@gmail.com> writes:
>
>> Timothy <tecosaur@gmail.com> writes:
>>
>>> On this, would you have any interested in going back to that thread
>>> about IDs generated based on the headings? IIRC it petered out more that
>>> reached a conclusion.
>>
>> I thought the conclusion was that if you wanted link stability, use
>> publish rather than export?
>
> No conclusion on the viability of my approach being modified a bit then
> integrated into Org.
Perhaps I misunderstood. My reading was that none of the proposed
approaches were complete enough (in the sense they either introduced
other issues or, while addressing some corner cases, made it much harder
to address others, broke or failed to cater for other workflows).
I was left with the general impression that solving this issue required
a significant amount of re-development and a far more sophisticated
approach for tracking, caching/memoizing IDs and attempting to address
the issues just by patching the existing code was only going to make
small improvements while complicating the existing code and making it
harder to maintain. In short, a significant re-design and
re-implementation effort rather than application of patches on the
existing code base is required and until someone can do this work, the
best approach was to use publish instead of export if link stability was
required.
--
Tim Cross
next prev parent reply other threads:[~2021-05-30 7:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 18:18 HTML export uses anchor ids which change on every export 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 [this message]
2021-05-30 12:11 ` Nicolas Goaziou
2021-06-08 23:31 ` Spencer Baugh
2021-06-09 12:19 ` Nicolas Goaziou
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=87r1ho8z6f.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@gmail.com \
/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).