On Tue, Apr 07, 2026 at 04:31:17PM +0800, aidan wrote:
> * for stand-alone info 7.2:
>
> 1. execute the command: info texinfo
> 2. press "u", we return to the dir node, the cursor is on the first line:
>
> File: dir, Node: Top This is the top of the INFO tree
>
> * for stand-alone info 7.3dev (50dc4a8d)
>
> 1. execute the command: info texinfo
> 2. press "u", we return to the dir node, the cursor is on the line:
>
> * dir 1: (/usr/local/share/info/dir)Top.
>
> * for emacs info mode:
>
> 1. evaluate: (info "texinfo")
> 2. press "u", we return to the dir node, the cursor is on the line:
>
> * Texinfo: (texinfo). The GNU documentation format.
>
>
>
> Generally, when using M-x up-node, the cursor should jump to the
> corresponding item in the menu of the up node.
Thanks for the report. I have reinstated the behaviour from Texinfo 7.2 (commit
8b145aa693), which was to go to the top of the dir node. Info 7.3 was
matching the "Top" node in the reference, which was inappropriate.
(If the dir file had had references naming a "Top" node, the same problem
could have occurred with Info 7.2).
The behaviour from Emacs would make more sense, but when the dir node is
made up of multiple files, it's possible some of the menu entries may not
go where you expect, with the current implementation. For example, I
have /usr/local/share/info/dir with this entry:
* msginit: (gettext)msginit Invocation.
Create a fresh PO file.
I also have /usr/share/info/dir with this entry:
* msginit: (gettext)msginit Invocation.
Create a fresh PO file.
These should go to different files (one under /usr/local/share/info, one
under /usr/share/info), but currently they go to the same place, whichever
entry in the composite dir node you follow.
"info -a msginit" works correctly. This produces the following menu:
* 1: (/usr/local/share/info/gettext.info)msginit Invocation.
* 2: (/usr/share/info/gettext.info.gz)msginit Invocation.
* 3: (*manpages*)msginit.
There both Info files can be accessed.
> Therefore, for these three behaviors, I think Emacs' Info mode is the most
> reasonable. The behavior in Info 7.2 is also acceptable, but the current
> behavior in Info 7.3dev seems very strange to me.
