On 11/24/20 7:22 PM, Abhilash Raj wrote:
I think I should keep in mind next time to use the #<heading-name> like
#3.3.2pointed out by Torge, instead of#id(which is what I see when I hover over the Link in browser so I copied ;).
It's more complicated than that. Sometimes the fragment name is the
heading and sometimes it is #idn. At the moment, neither #3.3.2 nor
#3.3.3 work at all as these are #id2 and #id1 respectively. Currently
the fragment for 3.3.3 Bugs is #bugs and the fragment for 3.3.2 Bugs is
#id3, but presumably prior to the addition of 3.3.3, #bugs was Bugs
under 3.3.2, Just as now, #command-line is Command line under 3.3.2, but
when a Command line section is added under 3.3.3, that will probably get
the command-line id.
Thus, the note "Permalink to this headline" es misleading at best because it isn't very permanent fo an evolving document.
You can specify explicit anchor name in .rst too, I think just adding a
.. _news-3.3.2just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading.
I too think this is correct. I suppose it might be worth doing for
NEWS.rst in particular since Sphinx doesn't seem to like fragments like
n.n.n. Another way to deal with this would be to always use code names.
It seems like a heading n.n.n will always get a #idn id, but, e.g.
3.3.0 – “Tom Sawyer” gets #tom-sawyer
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan