From: Howard Melman <hmelman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: "51240@debbugs.gnu.org" <51240@debbugs.gnu.org>
Subject: bug#51240: [External] : bug#51240: 27.2; Binding find-library commands
Date: Mon, 3 Jan 2022 18:02:11 -0500 [thread overview]
Message-ID: <09DAB10C-2D91-42CA-9558-F4EA3A108079@gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488708CC7523B09105824ACF3499@SJ0PR10MB5488.namprd10.prod.outlook.com>
On Jan 3, 2022, at 5:40 PM, Drew Adams <drew.adams@oracle.com> wrote:
>
>>> Thanks for the explanation, I think it makes sense to add
>>> C-x L, C-x 4 L, C-x 5 L to find-function-setup-keys.
>> Makes sense to me.
>
> Why is `L' needed, instead of `l', for `C-x [45]'?
> (Why should you need to use the Shift key for this?)
>
> Why is `C-x L' wasted on this? That `L' would be a
> perfectly good prefix key for something.
>
> Is a same-window key binding even needed? Do you
> really think it will be used much?
I answered all of these previously in this bug several months ago.
Juri and Lars agreed at the time, and I'm just trying to follow through to see the changes make it in.
Howard
next prev parent reply other threads:[~2022-01-03 23:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 16:49 bug#51240: 27.2; Binding find-library commands Howard Melman
2021-10-16 18:28 ` bug#51240: [External] : " Drew Adams
2021-10-16 18:57 ` Juri Linkov
2021-10-16 19:33 ` Drew Adams
2021-10-17 16:59 ` Juri Linkov
2021-10-17 1:16 ` Howard Melman
2021-10-17 17:04 ` Juri Linkov
2021-10-18 7:32 ` Lars Ingebrigtsen
2022-01-03 21:25 ` Howard Melman
2022-01-03 22:40 ` bug#51240: [External] : " Drew Adams
2022-01-03 23:02 ` Howard Melman [this message]
2022-01-03 23:32 ` Drew Adams
2022-01-04 0:04 ` Howard Melman
2022-01-04 15:36 ` Drew Adams
2022-06-30 10:49 ` bug#51240: bug#52074: 29.0.50; Add key binding for find-library Lars Ingebrigtsen
2022-06-30 15:40 ` 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
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=09DAB10C-2D91-42CA-9558-F4EA3A108079@gmail.com \
--to=hmelman@gmail.com \
--cc=51240@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 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).