all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
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 11:11:20 +0000	[thread overview]
Message-ID: <87k0503twn.fsf@posteo.net> (raw)
In-Reply-To: <83v8ok3ve7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 16 Oct 2022 13:39:12 +0300")

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?

One place I thought could make sense would be the
`startup-echo-area-message' prompt, but that doesn't look like it has
enough space.





  reply	other threads:[~2022-10-16 11:11 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 [this message]
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=87k0503twn.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 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.