[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: feature request for stand-alone info

From: Benno Schulenberg
Subject: Re: feature request for stand-alone info
Date: Sun, 14 May 2017 12:48:06 +0200

On Sat, May 13, 2017, at 13:38, Gavin Smith wrote:
> If we forget about what Info does already, and ask what the "right 
> thing" is, what's the answer? What's the most intutitive and powerful
> interface? Up and Down to scroll the page and Tab and S-Tab/M-Tab to 
> move between links?

I would say yes, because that is what web browsers like Firefox and
Chromium do.  That is what most people will be familiar with.

> I looked at the Lynx web browser and it uses Up and Down for both 
> scrolling and moving between links. It will only scroll if there are no
> more links on the currently-displayed part of a page.

Yes, another infuriating interface, because it is unobvious how to
scroll the screen just a few lines.  Only after looking at help,
one learns about ^N and ^P, but those are awkward to type for just
a little scrolling.  And: they get stuck when they land on an input
field.  Argh.

> > The best would be to let scroll-behavior affect also also the down-line
> > and up-line commands, and bind those by default to the arrow keys.
> This would be an easy change to make, but some people might hold down 
> Down to go to the end of the node but not want to go to the next node.
> Any change could be confusing and disorienting for people who are used
> to the current behaviour.

The current default behavior (no options, no .infokey) already /is/ that
<Down> passes across node boundaries, so there won't be any surprises
there.  This change was made a few years ago, and nobody complained,
so I doubt anyone will complain about down-line and up-line getting
more "far-reaching".


http://www.fastmail.com - The professional email service

reply via email to

[Prev in Thread] Current Thread [Next in Thread]