On Sun, Aug 10, 2025 at 11:31:40AM +0200, Patrice Dumas wrote:
> On Wed, Aug 06, 2025 at 11:51:30PM +0100, Gavin Smith wrote:
> > On Wed, Jul 09, 2025 at 01:52:24PM +0100, Gavin Smith wrote:
> > > Currently running "info texinfo menu" with the current output from
> > > texinfo.texi does not go to the node you expect ('Menus'), but to the
> > > documentation of the Info format instead ('Info Format Menu').
> > >
> > > ...
> > >
> > > Does one of the following sound like a good idea?:
> > >
> > > * Do not use @menu blocks when generating a detailed menu.
> > > * If reusing a @menu block to generate a detailed menu, then revise it
> > > never to a separate menu entry label.
> >
> > I've committed a change not to use a menu block if it has a separate
> > menu entry label in any of the menu entries. It could have been possible
> > only to omit or rewrite the menu entries that were affected, rather than
> > the entire menus, but I found it simpler to implement it this way. I expect
> > it should only make a difference on rare occasions.
>
> There is a difference, all the manual descriptions are omitted in the
> rewritten menu block. I do not known if it is important enough to
> justify another implementation, though.
If the user uses a @nodedescription line next to the referenced node, then
the description is used in the detailed menu.
I don't think it would be an important omission, as it would only make a
difference if the user does not have their own @detailmenu block in the Top
node. If they've moved away from explicit @menu blocks then it's likely
they are starting to use @nodedescription lines.
