From: Drew Adams <drew.adams@oracle.com>
To: Phil Sainty <psainty@orcon.net.nz>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: Manuel Uberti <manuel.uberti@inventati.org>,
"52074@debbugs.gnu.org" <52074@debbugs.gnu.org>
Subject: bug#52074: [External] : bug#52074: 29.0.50; Add key binding for find-library
Date: Wed, 24 Nov 2021 21:06:56 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488C21D0250025B04829D11F3619@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <8cbad051-6fa0-958a-d2a6-4ba1ab1b7361@inventati.org>
[Sending again. Didn't show up in the bug list for some reason.]
> Library commentaries are one of the primary sources of documentation
> in Emacs, so I think it's pretty help-related.
True. But we also have `finder-commentary' for that aspect.
> FWIW I use this same binding, and in my mind it makes excellent sense
> to use C-h C-l for `find-library' if you also have:
>
> C-h C-v for `find-variable'
> C-h C-f for `find-function'
> C-h C-k for `find-function-on-key'
>
> All of which feel (to me) analogous to C-h v, C-h f, and C-h k: Without
> the Ctrl modifier you view the docstrings; with it you view the code.
>
> (Admittedly C-h l is unconnected, but that hasn't bothered me.
> Following
> my pattern that would probably be bound to `finder-commentary', but I'm
> not suggesting we move `view-lossage' elsewhere.)
>
> I guess my main point is that I do think of *all* of these things as
> help-related, as I consider reading the code as just the next step up
> from reading the docstrings.
It's good to discuss this, and I'm glad to see
people giving _reasons_ for proposals/opinions.
I wish that were more often the case.
To my mind `find-library' fits most closely with
`find-file'. I put my `other-window' version on
`C-x 4 l' as analogy to `C-x 4 f'.
prev parent reply other threads:[~2021-11-24 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 6:54 bug#52074: 29.0.50; Add key binding for find-library Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 7:20 ` Lars Ingebrigtsen
2021-11-24 7:26 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 17:16 ` Lars Ingebrigtsen
2021-11-24 18:29 ` Juri Linkov
2021-11-24 18:55 ` bug#52074: [External] : " Drew Adams
2021-11-24 12:00 ` Phil Sainty
2021-11-24 18:21 ` bug#52074: [External] : " Drew Adams
2021-11-24 18:32 ` Drew Adams
2021-11-24 21:06 ` 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=SJ0PR10MB5488C21D0250025B04829D11F3619@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=52074@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=manuel.uberti@inventati.org \
--cc=psainty@orcon.net.nz \
/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).