From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58543@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>,
Stefan Kangas <stefankangas@gmail.com>
Subject: bug#58543: 29.0.50; The 'q' key is not shown by "C-h ?"
Date: Sun, 16 Oct 2022 11:49:53 +0200 [thread overview]
Message-ID: <87mt9wjdxa.fsf@gnus.org> (raw)
In-Reply-To: <838rlh77cy.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 Oct 2022 12:40:13 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> As Subject says: "C-h ?" doesn't show the 'q' key, it shows this
> instead:
>
> M-x help-quick-or-quit Display the quick help buffer.
>
> This is sub-optimal, I think, and will help users who need this "quick
> help" less than it could be.
>
> Thinking about it, perhaps 'q'; should be on the first line shown by
> "C-h ?".
Hm... It's rather confusing all over now. All the other commands after
`C-h ?' do the same as typing the commands directly.
That is, `C-h t' shows the Emacs tutorial, and `C-h ? t' does the same.
`C-h q' shows the quick help, but `C-h ? q' doesn't -- it just exits
`help-for-help'.
But the help-for-help says that it "Display the quick help buffer.",
which is only correct when you haven't `C-h ?' first.
So this is confusing on several different levels at the same time, and I
don't know what the best fix here would be.
Perhaps Philip of Stefan has some ideas; added to the CCs.
next prev parent reply other threads:[~2022-10-16 9:49 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mt9wjdxa.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58543@debbugs.gnu.org \
--cc=eliz@gnu.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 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.