From: Yuri Khan <yuri.v.khan@gmail.com>
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: Sat, 8 Jul 2023 03:11:39 +0700 [thread overview]
Message-ID: <CAP_d_8UToJRwWjaorWdiR2N5M7KLAXb_0-0Y+x9xYGg2vDgL0g@mail.gmail.com> (raw)
In-Reply-To: <83cz13ecix.fsf@gnu.org>
On Sat, 8 Jul 2023 at 02:40, Eli Zaretskii <eliz@gnu.org> wrote:
> > > And how will we tell the user that 'q' quits? In the echo-area,
> > > perhaps?
> >
> > Echo area, or header line, or mode line, whatever.
>
> Which is what we do now about SPC, and that is deemed not good enough.
> How is showing 'q' there suddenly better?
I cannot answer this because you’ve disagreed with the point that
explains it. (Namely, that users expect to be able to read without
having to be told about how to read, and do not expect the help
disappearing when they try to read it.)
next prev parent reply other threads:[~2023-07-07 20: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
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 [this message]
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=CAP_d_8UToJRwWjaorWdiR2N5M7KLAXb_0-0Y+x9xYGg2vDgL0g@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--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).