On Mon, Sep 28, 2026 at 08:13:31AM +0300, Eli Zaretskii wrote: > What about the @detailmenu used by large manuals? E.g., Emacs uses it > in 2 of its manuals. This menu includes all the nodes from the entire > manual, but the automatically-generated nodes will be absent from > there, won't they?
No, they will be present, the addition of nodes for sectioning commands is done before the automatic generation of menu and detailmenu. > There's also the issue of stuff that can appear in section names, but > is not recommended for node names (colons, Texinfo commands, etc.). What needs to be protected in the Texinfo code is protected (comma, leading parenthesis, colons...), and in the generated Info, the node name is also quoted if needed. Texinfo commands are fine in node names. As a side note, it would be good if quoted nodes in Info were recognized by the Emacs Info reader, for this purpose and others. There is a bug I opened: https://lists.gnu.org/archive/html/bug-gnu-emacs/2022-08/msg01756.html > More generally, I don't understand why it would be a good idea to make > this the default. It is a useful feature, but why make it the > default? Is the intent to invite authors of the Texinfo manuals not > to name the nodes? Exactly. In the long term, it would be easier for documentation writers if node names are optional. -- Pat
