On Fri, Oct 23, 2026 at 11:52:25PM +0200, Patrice Dumas wrote: > Hello, > > I think that the use case of AUTO_SECTION_NODE=0 with explicit @node > commands to separate the regions of the manual that should be placed in > different output files explained in "Global Customization Variables" > AUTO_SECTION_NODE is relevant enough to have its own section in the > "Nodes" chapter. It is actually used and could allow to do > better-looking Info or HTML manuals. I propose to put that section > before "Unstructured Nodes", and also add an example. > > Any objection?
AUTO_SECTION_NODE is specific to texi2any and doesn't mean anything for texinfo.tex. However, we do mention texi2any throughout the "Nodes" chapter (e.g. node pointer or menu generation), so I suppose AUTO_SECTION_NODE fits in here. I would like to keep the "Nodes" chapter still mainly about the Texinfo language per se, not about options of the Texinfo processors. It should be possible to read and understand this chapter without understanding what AUTO_SECTION_NODE does in texi2any output, so we should avoid adding mentions of AUTO_SECTION_NODE throughout the chapter, or presenting the idea that there are two different versions of the Texinfo language that the reader has to understand. The "Unstructured Nodes" node is not processor-specific (its contents are equally relevant regardless of whether you are processing with texi2any or texinfo.tex), so one suggestion is to put a new section *after* this node, as the other later sections in the chapter are more specific to texi2any (@nodedescription and @menu). I still plan to do more revision of the discussions of nodes and sections throughout the manual.
