unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bob Rogers <rogers@rgrjr.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: No more "Prefix Command" in C-h m
Date: Sun, 19 Mar 2023 10:58:40 -0700	[thread overview]
Message-ID: <25623.19792.452772.51937@orion.rgrjr.com> (raw)
In-Reply-To: <838rfsabfl.fsf@gnu.org>

   From: Eli Zaretskii <eliz@gnu.org>
   Date: Sun, 19 Mar 2023 19:38:38 +0200

   > From: Bob Rogers <rogers@rgrjr.com>
   > Date: Sun, 19 Mar 2023 10:19:37 -0700
   > 
   >    A while ago, I noticed that C-h m no longer shows keys bound to

   You mean "C-h b", I suppose.

Yes (but I'm used to seeing them in C-h m output).

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

   He already did, see

     https://lists.gnu.org/archive/html/emacs-devel/2021-10/msg02399.html
     https://lists.gnu.org/archive/html/emacs-devel/2021-10/msg02402.html

   Bottom line: they were deemed unnecessary, since the key bindings that
   use the prefix also show the prefix.

Thanks.

   We could add a user option to get that back, if we think people will
   want that sometimes.

I would prefer that, since it's what I'm used to.  I would argue that
the default should be on, since it almost tripped me up once.  But it's
probably more of a legacy thing, and in any case I suppose that ship has
sailed.

   If adding the option is deemed desirable, I'd be happy to code it.

					-- Bob



  reply	other threads:[~2023-03-19 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 17:19 No more "Prefix Command" in C-h m Bob Rogers
2023-03-19 17:38 ` Eli Zaretskii
2023-03-19 17:58   ` Bob Rogers [this message]
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.19792.452772.51937@orion.rgrjr.com \
    --to=rogers@rgrjr.com \
    --cc=eliz@gnu.org \
    --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).