From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "14084@debbugs.gnu.org" <14084@debbugs.gnu.org>
Subject: bug#14084: 24.3.50; `substitute-command-keys': allow for expansion of <remap>...
Date: Thu, 9 Jun 2022 15:36:21 +0000 [thread overview]
Message-ID: <SJ0PR10MB548852E4BC02B882CD27E1C4F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87a6al3nma.fsf@gnus.org>
> > 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
The request was to please add an optional arg to
`substitute-command-keys' that changes the behavior.
IOW, give code control - and in the ways suggested.
So ... "won't fix". You ignored the request and did
what you wanted from the beginning for a different
problem you saw: just foo and bar being far apart.
prev parent reply other threads:[~2022-06-09 15:36 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
2022-06-09 15:36 ` Drew Adams [this message]
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=SJ0PR10MB548852E4BC02B882CD27E1C4F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=14084@debbugs.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).