all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / 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 19:11:01 +0000	[thread overview]
Message-ID: <p2PYCIh1XHUl48aR-KF-_J--A8UTf77sVgjHdcc_3eO_ro7MeXLOLR8fpSqhoqrTsjjWpmo6mb8M7qt9dsBSF1OwyVSokMENBh1wmQSz4Xc=@proton.me> (raw)
In-Reply-To: <83mt07ee2n.fsf@gnu.org>

------- Original Message -------
On Saturday, July 8th, 2023 at 7:06 AM, Eli Zaretskii <eliz@gnu.org> wrote:


> > From: Yuri Khan yuri.v.khan@gmail.com
> > Date: Sat, 8 Jul 2023 01:28:29 +0700
> > Cc: help-gnu-emacs@gnu.org
> > 
> > On Fri, 7 Jul 2023 at 13:39, Eli Zaretskii eliz@gnu.org wrote:
> > 
> > > > 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.
> > 
> > ‘help-mode-map’ has ‘q’ bound to ‘quit-window’ and that’s the minimal
> > fuss way to return from the help window. It also would help build
> > habits that work with a wide set of buffers in Emacs.
> 
> 
> And how will we tell the user that 'q' quits? In the echo-area,
> perhaps?
> 
> > As it is, the user has to build three sets of habits: (1) for the
> > rudimentary Info-summary modal event loop where SPC scrolls up and
> > anything else quits; (2) for modes that inherit from special-mode
> > where SPC scrolls up, DEL and S-SPC scroll down, ‘q’ quits, and all
> > familiar keys work; and (3) for the full experience editable buffers
> > where you have to scroll with Page Up/Down and have no notion of
> > quitting.
> 
> 
> You exaggerate the problem. A typical user of computers these days
> needs much more than 3 sets of habits for similar actions. And
> scrolling with SPC in Emacs is quite a widely-used paradigm.

How does one scroll up again, it is not evident how.
 
> > > 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.
> > 
> > (Hand-written whitespace-ignoring minimal diff follows. I signed the
> > paperwork some time ago and it should be valid for now.)
> 
> 
> Thanks, but this is not the right place for posting patches.



  reply	other threads:[~2023-07-07 19:11 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
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 [this message]
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

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

  git send-email \
    --in-reply-to='p2PYCIh1XHUl48aR-KF-_J--A8UTf77sVgjHdcc_3eO_ro7MeXLOLR8fpSqhoqrTsjjWpmo6mb8M7qt9dsBSF1OwyVSokMENBh1wmQSz4Xc=@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.