Thank you, the issue has now been fixed.

At the same time, I noticed that in the commit c5fb1eed you changed the
behavior of messages.

When scroll-behavior=Page Only, the previous messages for
move-to-next/prev-xref (“You are already at the first/last page of this
node”) were indeed misleading. However, there is now no message at all,
which is somewhat inconvenient. It would be helpful if a message could be
added in this case.


This is the commit:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
commit c5fb1eedf2fe1f2a68b8b573ad6e03dd38d16d03
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Author: Gavin Smith <[email protected]>
Date:   Thu Apr 2 22:13:41 2026 +0100

    Remove misleading messages for move-to-next/prev-xref.

    * info/session-cmd.c
    (forward_move_node_structure, backward_move_node_structure)
    [scroll-behaviour=Page Only]: Do not print message saying we
    are already on the last (or first) page of a node.  This may
    not be true if called via move-to-next-xref (or move-to-prev-xref).

    (point_next_line, point_prev_line, _scroll_backward, _scroll_forward):
    Reinstate the removed messages for cursor movement and scrolling
    commands where they would be accurate.


On Fri, Apr 3, 2026 at 5:15 AM Gavin Smith <[email protected]> wrote:

> On Thu, Apr 02, 2026 at 10:11:42PM +0800, aidan wrote:
> > 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.
> >
> >
> >
> >
> > Among the six cases, only the fourth is the one I consider problematic
> and
> > should be fixed
> >
>
> Thanks for the thorough testing.  It was indeed a bug:
>
> diff --git a/info/session-cmd.c b/info/session-cmd.c
> index 20821d194c..10df74767b 100644
> --- a/info/session-cmd.c
> +++ b/info/session-cmd.c
> @@ -1825,7 +1825,7 @@ DECLARE_INFO_COMMAND (info_move_to_prev_xref,
>                return;
>              }
>
> -          if (backward_move_node_structure (window, info_scroll_behaviour
> != 0)
> +          if (backward_move_node_structure (window,
> info_scroll_behaviour) != 0
>                || !strcmp (window->node->nodename, initial_nodename))
>              {
>                break; /* No earlier nodes in file, or we are back where we
>
>
> I've committed this fix in the git repository.
>

Reply via email to