> Date: Sun, 9 Jan 2022 09:32:38 -0800 > From: Per Bothner <p...@bothner.com> > > An idea I've been mulling: Currently, we handle changes in node structure > by generating extra stub pages that redirect to the correct location. > This works, but it's a bit clunky. For one thing, it doesn't update > the location bar (though that could be fixed). Worse, it highlights a > two-level name hierarchy FILENAME.html#FRAGMENT that depends on > the splitting mode. > > Instead, I suggest that the primary and visible name for every node and anchor > use the fragment names (the part after the '#'). > > For example, the Keys chapter in the Emacs manual would still be in the > file Keys.html, and you can still browse to > "https://whatever/emacs/Keys.html";. > However, the "perma-link" would be "https://whatever/emacs#Keys";, and that > is what would show in the location bar. Currently, 'Keys" is a section, > but the perma-link would remain "emacs#Keys" regardless of whether > it is changed to a chapter or subsection, or of the splitting mode. > Even if the section is renamed, "emacs#Keys" would work as long as > an @anchor with the old name is added.
I'm not sure I understand what will happen with @anchor's.
