From: Bob Rogers <rogers@rgrjr.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: No more "Prefix Command" in C-h m
Date: Sun, 19 Mar 2023 10:19:37 -0700 [thread overview]
Message-ID: <25623.17449.499467.806822@orion.rgrjr.com> (raw)
A while ago, I noticed that C-h m no longer shows keys bound to
keymaps as "Prefix Command" along with their siblings when I almost
clobbered such a prefix when looking for an unused key sequence. I was
about to submit a bug report when I noticed the comment in the code that
said this was a design choice. The commit was a5d79fcfe83e by Lars
Ingebrigtsen on 2021-11-01. Lars, would you please tell us why?
-- Bob Rogers
http://www.rgrjr.com/
next reply other threads:[~2023-03-19 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 17:19 Bob Rogers [this message]
2023-03-19 17:38 ` No more "Prefix Command" in C-h m Eli Zaretskii
2023-03-19 17:58 ` Bob Rogers
2023-03-19 18:20 ` 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=25623.17449.499467.806822@orion.rgrjr.com \
--to=rogers@rgrjr.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.
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).