Re: Stand-alone Info and info-mode inconsistency: end of buffer behavior

[Eli Zaretskii]

> From: Gavin Smith <gavinsmith0123@gmail.com>
> Date: Fri, 6 Jan 2023 22:02:54 +0000
> Cc: Eli Zaretskii <eliz@gnu.org>, bug-texinfo@gnu.org
> 
> On Fri, Jan 06, 2023 at 09:23:17PM +0100, Arsen Arsenović wrote:
> > Evening Eli,
> > 
> > Eli Zaretskii <eliz@gnu.org> writes:
> > 
> > > That's not true, or at least that's not what I see on my system.  The
> > > Emacs Info reader goes to the next node when it reaches the end of the
> > > current node.  Maybe your Emacs has some customizations?  If you see
> > > the Emacs behavior you describe in "emacs -Q", please describe exactly
> > > what you do to reproduce the behavior: which manual you load and what
> > > commands/keys you type after that.
> > 
> > Reproduction steps that work for me:
> > 
> > 1. emacs -Q --eval '(info "(info)Top")'
> > 2. M->
> > 3. C-n
> > 
> > The (info)Top node on my system has a next node ("(info)Getting
> > Started"), which pure ``n'' and (Info-next) take me to, but none of the
> > in-buffer navigation commands (including <PageUp>/<PageDown>) do.
> 
> This can be configured using the scroll-behaviour and cursor-motion-scrolls
> variables in .infokey (see Info node (info-stnd)Variables).
> 
> The info-stnd manual starts,
> 
>   You can read through the rest of this manual by typing <SPC> and <DEL>
>   (or <Space> and <Backspace>)
> 
> I doubt would help to stop this from working and leave the user stuck
> on the Top node.

He means C-n, not SPC.  SPC behaves the same in Emacs as it does in
the standalone Info.  That's why I originally misunderstood the
report: I though SPC was being used.