unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58543@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
	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 10:21:05 +0000	[thread overview]
Message-ID: <87wn903w8e.fsf@posteo.net> (raw)
In-Reply-To: <87mt9wjdxa.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 16 Oct 2022 11:49:53 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> 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.

It was probably wrong to add `help-quick-or-quit' to C-h ? in the first
place.  My proposal to bind C-h q to `help-quick-or-quit' was that "C-h
q" had no effect *outside of* the Metahelp buffer.  But of course, in
the Metahelp buffer "q" does have an effect, that overrides
`help-quick-or-quit'.  My guess is that that is the reason why the
binding is displayed using M-x.

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.





  reply	other threads:[~2022-10-16 10:21 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 [this message]
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

  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=87wn903w8e.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=58543@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --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).