Thank you for your reply! I discovered that the behavior was actually caused by the scroll-behavior and cursor-movement-scrolls variables in my infokey file.
1. scroll-behavior=Continuous cursor-movement-scrolls=Off In this case, both commands cycle through the cross-references in a single node. 2. scroll-behavior=Continuous cursor-movement-scrolls=On In this case, both commands follow the "Continuous" scroll behavior (i.e. can jump to any xref in the current Info document) 3. scroll-behavior=Page Only cursor-movement-scrolls=Off In this case, both commands cycle through the cross-references in a single node. 4. scroll-behavior=Page Only cursor-movement-scrolls=On In this case, only move-to-next-xref follow the "Page Only" scroll behavior (i.e. just stops at node boundaries) while move-to-prev-xref behaves like case 6 (see below). This is the case described in the original report. 5. scroll-behavior=Next Only cursor-movement-scrolls=Off In this case, both commands cycle through the cross-references in a single node. 6. scroll-behavior=Next Only cursor-movement-scrolls=On In this case, both commands follow the "Next Only" scroll behavior (i.e. can jump to any xref in the sibling nodes) Among the six cases, only the fourth is the one I consider problematic and should be fixed On Thu, Apr 2, 2026 at 6:11 PM Gavin Smith <[email protected]> wrote: > On Tue, Mar 24, 2026 at 10:06:51AM +0800, aidan wrote: > > Hello Texinfo maintainers, > > > > Thank you for your work on Texinfo. > > > > I believe I may have found a bug: > > > > *Version:* > > > > info (GNU texinfo) 7.2 > > > > *Environment:* > > > > 6.19.6-arch1-1 > > > > *Steps to reproduce:* > > > > *1. run stand-alone info reader: `*info "(texinfo)Output Formats"*`* > > > > *2. press shift+tab (or M-x *move-to-prev-xref*)* > > > > *Expected behavior:* > > > > The node "(info-stnd)Selecting Xrefs" says: > > > > <TAB> (‘move-to-next-xref’) > > Move the cursor to the start of the next nearest menu item > or > > note > > reference in this node. You can then use <RET> > > (‘select-reference-this-line’) to select the menu or note > > reference. > > > > ‘M-<TAB>’ (‘move-to-prev-xref’) > > ‘BackTab’ > > Move the cursor the start of the nearest previous menu item > or > > note > > reference in this node. > > > > The ‘BackTab’ key can be produced on some terminals with > > ‘Shift-<TAB>’. > > > > so both move-to-next-xref and move-to-prev-xref should not cross node > > boundaries. While move-to-next-xref behaves as expected, > move-to-prev-xref > > can cross into a previous node > > Thanks for the report. In my testing, both commands cross node > boundaries. This is expected. > > I believe it is due to the setting of the 'cursor-movement-scrolls' > variable. If I run "info -v cursor-movement-scrolls=Off", then TAB > and M-TAB only cycle through the cross-references in a single node, > if there are any. > > I suppose the manual could be changed to take out the text like "in > this node" so that it is accurate. > > > > > > > move-to-prev-xref should do nothing in this case > > > > *Actual behavior:* > > > > The cursor moves to a previous node, on "(standards)Change Logs" >
