From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: master f0cd91067d: Improve `C-h b' output for remapped commands.
Date: Fri, 10 Jun 2022 09:01:49 -0400 [thread overview]
Message-ID: <jwvv8t8he1k.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87pmjgx4xa.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 10 Jun 2022 11:07:29 +0200")
> Hm... What about just flipping things around and using our words?
> That would also make the lines shorter. I.e.,
>
> C-x 4 C-o ido-display-buffer
> (Remapped via <remap> <display-buffer>.)
> C-x 5 C-o ido-display-buffer-other-frame
> (Remapped via <remap> <display-buffer-other-frame>.)
Sounds good to me. I don't have an opinion on the specific wording
within the parens, but I'll mention that a single `remap display-buffer`
can cause various key bindings to be remapped, which is why I suggested
<remap> <display-buffer> ido-display-buffer
C-x 4 C-o
which naturally generalizes to things like:
<remap> <display-buffer> ido-display-buffer
C-x 4 C-o, C-c C-o C-o
Also, a remap entry can have 0 corresponding keybindings, in which case
we should keep something like
<remap> <display-buffer> ido-display-buffer
-- Stefan
next prev parent reply other threads:[~2022-06-10 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165478576035.737.9544262446139689575@vcs2.savannah.gnu.org>
[not found] ` <20220609144240.9D08DC01682@vcs2.savannah.gnu.org>
2022-06-09 16:44 ` master f0cd91067d: Improve `C-h b' output for remapped commands Stefan Monnier
2022-06-09 17:45 ` [External] : " Drew Adams
2022-06-10 9:07 ` Lars Ingebrigtsen
2022-06-10 11:23 ` Stefan Kangas
2022-06-10 12:07 ` Michael Heerdegen
2022-06-10 13:02 ` Po Lu
2022-06-10 13:13 ` Michael Heerdegen
2022-06-11 10:36 ` Lars Ingebrigtsen
2022-06-10 13:01 ` Stefan Monnier [this message]
2022-06-11 10:48 ` Lars Ingebrigtsen
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=jwvv8t8he1k.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 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.