unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Howard Melman <hmelman@gmail.com>,
	"51240@debbugs.gnu.org" <51240@debbugs.gnu.org>
Subject: bug#51240: [External] : bug#51240: 27.2; Binding find-library commands
Date: Sat, 16 Oct 2021 18:28:43 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488A0CFA0D453F62298819BF3BA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <F8C28E33-0B28-498C-BFC0-409C51B15F4A@gmail.com>

> I see that the other-window and other-frame versions of
> find-library were added in Emacs 26 but none of them were
> bound to keys as discussed in Emacs bug#26712.  And if I'm
> looking at the correct source tree, still aren't bound in
> Emacs 28.  It seemed like there was concensus on replacing
> the bindings of the find-function commands with new
> find-function-or-library versions but the included patches
> were never applied and the bug archived.
> 
> There was also discussion in bug#2270 that also didn't seem
> to come to resolution.
> 
> I (bind and) use find-library all the time, typically to
> view the source of a 3rd party package I've installed via
> elpa (since entering the package name is easier than a
> function name).  Is there a better way to do this?  If not,
> could these commands be bound (possibly in Emacs 28)?

+1.

[But isn't this essentially bug #26712? and 2270?
(which was closed as Done, but with no key binding)]

IMO, we should bind `find-library-other-window' to
`C-x 4 l' and `find-library-other-frame' to `C-x 5 l'.
___

[And this is from someone who doesn't Emacs to waste
key bindings.  These bindings just make sense.  I
almost never use `find-library'.  I use `C-x 4 l'
(which, because I use non-nil `pop-up-frames', opens
in another frame).]
___

Maybe this will happen in another decade or two?...
I proposed this in 2007 (as soon as `find-library'
was added, if I'm not mistaken).





  reply	other threads:[~2021-10-16 18:28 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 ` Drew Adams [this message]
2021-10-16 18:57   ` bug#51240: [External] : " 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
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=SJ0PR10MB5488A0CFA0D453F62298819BF3BA9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=51240@debbugs.gnu.org \
    --cc=hmelman@gmail.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).