On Mon, Sep 28, 2026 at 05:36:29PM +0200, [email protected] wrote: > If the user wants to have nodes added for sectioning command, and also > manually generates the @detailmenu, it should be ok (according to my > testing).
I tested an explicit @menu referencing some of the implicit nodes, and it appears to output ok, including structure warnings for menus. For example: \input texinfo @node top @top in top. @menu * One:: * Three:: * Two:: @end menu @chapter One AA @node Two @chapter Two AA @chapter Three AA @bye Running "texi2any -c TREE_TRANSFORMATIONS=insert_nodes_for_sectioning_commands" on this input outputs the same warnings that would be output if explicit @node lines were present: shadow-structure.texi:10: warning: node `Three' in menu where `Two' expected shadow-structure.texi:11: warning: unexpected node `Two' in menu This suggests the feature works well with explicit menus, just treat the lone sectioning command as a @node. Without insert_nodes_for_sectioning_commands, there is no warning, which is probably because "One" and "Three" are created as anchors, not nodes, and they are not part of the document structure. This is not a major problem as insert_nodes_for_sectioning_commands should be becoming the default anyway. This may not currently work well with Emacs commands for updating menus in Texinfo source, but nobody is forcing anyone to use the new feature and it's possible for these Emacs commands to be changed in the future to recognise lone sectioning commands (without a precdeding @node command).
