On Sun, Jun 22, 2025 at 06:53:42PM +0100, Gavin Smith wrote: > @c Getopt and argp start at the @section level so that there's > @c enough room for their internal hierarchy (mostly a problem with > @c argp). -Miles > > As the comment says, "Getopt" is a @section although its superior node > is a @subsection. > > This could be an example of incorrect sectioning levels being the problem, > rather than an issue with menus. At the moment the only idea I have is > to also warn about the node up pointer mismatch at the same time.
I do not really understand the comment explaining why Getopt and argp start at the @section level, I do not get what "enough room for their internal hierarchy" means, so it is not clear to me why the Glibc people want that structure. But this seems to me to be a case of node structure differing from the sections structure that was done on purpose. This could be annoying if there is no possibility to silence the warnings. Regarding the HTML output, it does not look bad to me. I agree that a menu-like link from https://www.gnu.org/software/libc/manual/html_node/Parsing-Program-Arguments.html to https://www.gnu.org/software/libc/manual/html_node/Getopt.html would have been better, but the Parsing-Program-Arguments.html node is short and the links are available as xrefs. In addition, having links to Getopt.html in https://www.gnu.org/software/libc/manual/html_node/Program-Basics.html may be considered a good thing, as it allows to go straight to Getopt.html. -- Pat
