Re: stability of toc links

[Robert Weiner <rswgnu@gmail.com>]

I missed the beginning of this; what exactly are you looking for?  If you don’t want ids attached to the headlines that go into the toc, are you asking for code that automatically updates the toc on any change to individual headlines inthe document body?

It would probably be easier to just have a command like Texinfo has that regenerates its toc-like menus.

-- rsw

> On Oct 9, 2022, at 9:38 PM, Samuel Wales <samologist@gmail.com> wrote:
> 
> [i should clarify the clarification as i do not want it to seem like
> saying i already covered that was the only point for no reason.  what
> i meant is to provide context for those who are stumbling upon this
> long thread.
> 
> it seems an active topic and a lot of custom id solutins were
> presented and while custom id is a great feature, and provides a great
> solution for those who want it, and in many cases is a great solution,
> it is definitely not for /everybody/ in all cases, especially the
> particular case of a large document where /lots/ of headers might
> potentially be linked to by users, such as my original example in op,
> a /long/ blog post.  and thus lots of properties drawers and custom id
> identifiers would be created.  custom id is not a solution for me, for
> toc or any other links that i desire to be stable /automatically/,
> which is why i addressed them and id in my op and said "short of".
> 
> for clarity, according to my sensibilities, which others obviously
> will differ on, custom id is more suitable for the document author to
> use manually, and reasonably sparingly, and with particularly
> meaningful and carefully chosen names.  a custom id name refers to an
> internal link that was chosen out of many, and refers to it with
> semantic value attached.
> 
> in other words, to me, in most cases, custom id is not for code to
> generate.  in my own case, code would potentially create an enormous
> number of undesired properties drawers with custom ids and /also/ make
> it so that it is no longer as much of a semantically valuable feature
> that custom id were added manually sparingly and with meaningful names
> for  particularly potent internal links to draw the reader's or
> author's attention to or be straightforwardly searchable.  if that
> makes any sense there.  :)
> 
> [as for drawers, as an aside: to my sensibilities, too many make the
> document author wonder if they contain anything significant, require
> opening them to make sure they are ok, and take up space in the emacs
> window which in my case is highly limited.  also, they possibly reduce
> efficiency as at least in the past drawers were highly inefficient in
> org.  these issues probably do not apply to everybody.]
> 
> so that is why i said in the op "short of adding custom id or id to
> everything", and why i clarified that i mentioned what you brought up
> in the op.  sometimes i effectively assume that all my implications
> are understood when in fact i am supposed to spell them out but i am
> limited in computer use so i sometimes do not.  perhaps it helps
> clarify.]
> 
> 
>> On 10/9/22, Samuel Wales <samologist@gmail.com> wrote:
>>> On 12/8/20, Tom Gillespie <tgbugs@gmail.com> wrote:
>>> It sounds like you are looking for the CUSTOM_ID property.
>> 
>> just for clarity, i addressed this in my original post when i said
>> "short of adding custom id or id to everything".
>> 
> 
> 
> -- 
> The Kafka Pandemic
> 
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>