unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Howard Melman <hmelman@gmail.com>
Cc: "51240@debbugs.gnu.org" <51240@debbugs.gnu.org>
Subject: bug#51240: [External] : bug#51240: 27.2; Binding find-library commands
Date: Sun, 17 Oct 2021 20:04:17 +0300	[thread overview]
Message-ID: <87bl3n3ob2.fsf@mail.linkov.net> (raw)
In-Reply-To: <1512A8BF-E11B-4E31-8064-EC4E40D90BFB@gmail.com> (Howard Melman's message of "Sat, 16 Oct 2021 21:16:32 -0400")

> The other commands related to find-library are setup via
> find-function-setup-keys.  The equivalents of find-library
> are on C-x F, C-x K and C-x V and then on the C-x 4 and
> C-x 5 locations too.

> I use this often if I want to visit a library regardless of what is
> near point.  If I want to open embark (say because I just updated
> it), I use C-x L and enter "embark" via completing-read.
> It's very convenient.

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.





  reply	other threads:[~2021-10-17 17:04 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 [this message]
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=87bl3n3ob2.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --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).