From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 58543@debbugs.gnu.org, larsi@gnus.org, stefankangas@gmail.com
Subject: bug#58543: 29.0.50; The 'q' key is not shown by "C-h ?"
Date: Sun, 16 Oct 2022 14:42:45 +0300 [thread overview]
Message-ID: <83r0z83sga.fsf@gnu.org> (raw)
In-Reply-To: <87k0503twn.fsf@posteo.net> (message from Philip Kaludercic on Sun, 16 Oct 2022 11:11:20 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: larsi@gnus.org, 58543@debbugs.gnu.org, stefankangas@gmail.com
> Date: Sun, 16 Oct 2022 11:11:20 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Philip Kaludercic <philipk@posteo.net>
> >> Cc: Eli Zaretskii <eliz@gnu.org>, 58543@debbugs.gnu.org, Stefan Kangas
> >> <stefankangas@gmail.com>
> >> Date: Sun, 16 Oct 2022 10:21:05 +0000
> >>
> >> I would therefore remove entry from the "(make-help-screen
> >> help-for-help" block, and consider some other place to mention the quick
> >> help buffer.
> >
> > How about mentioning it in the "C-h" prompt itself?
>
> Do you mean the "C-h (Type ? for further options)-" prompt?
Yes. Make it say
C-h (Type ? for further options, q for quick help)-
or somesuch.
next prev parent reply other threads:[~2022-10-16 11:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 9:40 bug#58543: 29.0.50; The 'q' key is not shown by "C-h ?" Eli Zaretskii
2022-10-16 9:49 ` Lars Ingebrigtsen
2022-10-16 10:21 ` Philip Kaludercic
2022-10-16 10:39 ` Eli Zaretskii
2022-10-16 11:11 ` Philip Kaludercic
2022-10-16 11:42 ` Eli Zaretskii [this message]
2022-10-16 12:11 ` Stefan Kangas
2022-10-16 13:39 ` Philip Kaludercic
2022-10-16 14:03 ` Eli Zaretskii
2022-10-16 14:23 ` Lars Ingebrigtsen
2022-10-16 22:39 ` Philip Kaludercic
2022-11-04 22:59 ` Philip Kaludercic
2022-10-16 16:50 ` Stefan Kangas
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=83r0z83sga.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58543@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=philipk@posteo.net \
--cc=stefankangas@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).