>> 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?
HTML. > In Info, it seems to me that a @detailmenu is always right, as it > plays the same role as table of contents. Yep. > Do you set explicitly FORMAT_MENU to menu for HTML, Yes. > and if so, why do you prefer menus over the default 'sectiontoc'? Because we have a sidebar with exactly that, see https://lilypond.org/doc/v2.25/Documentation/changes/index.html for an example. >> 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, Given that a detailmenu in Info style looks very un-HTML-ish I think it would be best if `texi2any` didn't generate a detailmenu for HTML output by default if `FORMAT_MENU` is set to 'menu'. However, such a change wouldn't be backward-compatible, thus ... > 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. ... 'menu_no_detailmenu' sounds good to me. Werner
