unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: uzibalqa <uzibalqa@proton.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Pressing ? does not allow window scrolling through the list of info commands
Date: Fri, 07 Jul 2023 11:38:32 +0000	[thread overview]
Message-ID: <14KP-ia-06yjAh-_mSMzvtPr1r24o2Csrt1AZWdGWTTN2OfCHNEcTkbmUFJaAeHHZZmkW5S3QypOZdaAMZG9RnU-ApcaB8nsuaTXFphsZGg=@proton.me> (raw)
In-Reply-To: <837crcgra6.fsf@gnu.org>


------- Original Message -------
On Friday, July 7th, 2023 at 6:38 PM, Eli Zaretskii <eliz@gnu.org> wrote:


> > From: Yuri Khan yuri.v.khan@gmail.com
> > Date: Fri, 7 Jul 2023 13:00:30 +0700
> > Cc: help-gnu-emacs@gnu.org
> > 
> > However, what is the reason for that event loop?
> 
> 
> The reason is to allow return to the manual with minimal fuss. As the
> user who invokes "?" is very likely to be a newbie to Emacs, having
> them to deal with buffers and windows at this point is unwise, to say
> the least.

For newbies it is even more strange to see oneself getting diverted back
to the manual, considering that many are used to traverse a buffer with
the arrow keys or mouse scroll.  Particularly when such buffer scrolling
operations work as expected within the manual.  
 
> For the same reason, the first screenful displayed by "?" should show
> all of the essential commands, leaving the next screenful to show the
> advanced and more rarely-used ones.
> 
> I'm not saying I object to adding more keys to scroll the display
> there, but the simplicity of going back to the manual should be
> preserved.

The informational note about how to traverse the buffer shewn in the 
Echo Area should be written at the beginning, as soon as the newbie
(or not) gets to the '?' page.
 




  reply	other threads:[~2023-07-07 11:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  0:37 Pressing ? does not allow window scrolling through the list of info commands uzibalqa
2023-07-07  5:31 ` Eli Zaretskii
2023-07-07  6:00   ` Yuri Khan
2023-07-07  6:38     ` Eli Zaretskii
2023-07-07 11:38       ` uzibalqa [this message]
2023-07-07 11:40         ` uzibalqa
2023-07-07 12:54           ` Eli Zaretskii
2023-07-07 13:03             ` uzibalqa
2023-07-07 13:12               ` Eli Zaretskii
2023-07-07 13:46                 ` uzibalqa
2023-07-07 15:03                   ` [External] : " Drew Adams
2023-07-07 14:58               ` Drew Adams
2023-07-07 15:04                 ` uzibalqa
2023-07-07 14:51         ` Drew Adams
2023-07-07 18:28       ` Yuri Khan
2023-07-07 19:06         ` Eli Zaretskii
2023-07-07 19:11           ` uzibalqa
2023-07-07 21:58             ` Stephen Berman
2023-07-07 19:34           ` Yuri Khan
2023-07-07 19:40             ` Eli Zaretskii
2023-07-07 19:52               ` Eli Zaretskii
2023-07-07 19:57                 ` Jean Louis
2023-07-07 20:07                 ` uzibalqa
2023-07-07 20:11               ` Yuri Khan
2023-07-07 20:19                 ` uzibalqa
2023-07-07 19:48             ` uzibalqa
2023-07-07 19:08         ` [External] : " Drew Adams
2023-07-07 19:31       ` Jean Louis
2023-07-07 11:30   ` uzibalqa
2023-07-07 12:51     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='14KP-ia-06yjAh-_mSMzvtPr1r24o2Csrt1AZWdGWTTN2OfCHNEcTkbmUFJaAeHHZZmkW5S3QypOZdaAMZG9RnU-ApcaB8nsuaTXFphsZGg=@proton.me' \
    --to=uzibalqa@proton.me \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).