From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 14084@debbugs.gnu.org
Subject: bug#14084: 24.3.50; `substitute-command-keys': allow for expansion of <remap>...
Date: Thu, 09 Jun 2022 16:41:49 +0200 [thread overview]
Message-ID: <87a6al3nma.fsf@gnus.org> (raw)
In-Reply-To: <87y1z9h6nh.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 10 May 2022 15:13:54 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I think the `C-h b' output could perhaps be reorganised, because bar and
> foo frequently are displayed far apart, so the person looking for the
> key for bar would have to look around.
>
> We could, for instance, add an extra line here.
>
> But did you have other contexts in mind?
Apparently not, so I've now added code to Emacs 29 that results in this
sort of display:
<remap> <display-buffer> ido-display-buffer
C-x 4 C-o display-buffer
<remap> <display-buffer-other-frame> ido-display-buffer-other-frame
C-x 5 C-o display-buffer-other-frame
<remap> <insert-buffer> ido-insert-buffer
C-x x i insert-buffer
<remap> <kill-buffer> ido-kill-buffer
C-x k kill-buffer
<remap> <switch-to-buffer> ido-switch-buffer
C-x b switch-to-buffer
<remap> <switch-to-buffer-other-frame> ido-switch-buffer-other-frame
C-x 5 b switch-to-buffer-other-frame
<remap> <switch-to-buffer-other-window> ido-switch-buffer-other-window
C-x 4 b switch-to-buffer-other-window
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-09 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 5:17 bug#14084: 24.3.50; `substitute-command-keys': allow for expansion of <remap> Drew Adams
2022-05-10 13:13 ` Lars Ingebrigtsen
2022-05-10 15:30 ` Drew Adams
2022-05-10 15:50 ` Lars Ingebrigtsen
2022-05-10 16:03 ` Drew Adams
2022-05-10 16:06 ` Lars Ingebrigtsen
2022-05-10 16:28 ` Drew Adams
2022-06-09 14:41 ` Lars Ingebrigtsen [this message]
2022-06-09 15:36 ` Drew Adams
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=87a6al3nma.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=14084@debbugs.gnu.org \
--cc=drew.adams@oracle.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.