On Mon, Feb 24, 2025 at 06:27:39AM +0000, Werner LEMBERG wrote: > > I was just bitten by the undocumented feature that `texi2any` > generates a `@detailmenu` block if it auto-generates menus, and the > top-level menu of a document is not present.
Is it an issue for you for Info or HTML output format? In Info, it seems to me that a @detailmenu is always right, as it plays the same role as table of contents. Do you set explicitly FORMAT_MENU to menu for HTML, and if so, why do you prefer menus over the default 'sectiontoc'? > Please make this controllable. For example, an empty > > ``` > @detailmenu > @end detailmenu > ``` Looks too fragile and too much risk of unintended effects. > block at the top-level could indicate that a `@detailmenu` block > should be auto-generated. > > Another possibility would be a new command, say, `@nodetailmenu`, to > suppress the generation of a `@detailmenu` block. At least in a first step, a customization variable would be better, and I also think that most users want a detailmenu, so keeping it a customization variable could be the best in the long term too. A specific customization variable could be an options, another possibility could be to add another value for FORMAT_MENU, like menu_no_detailmenu. -- Pat
