From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 36767@debbugs.gnu.org, rpluim@gmail.com, emacsuser@freemail.hu,
larsi@gnus.org, juri@linkov.net
Subject: bug#36767: 26.1; request: add more quick keys to the *Help* buffer
Date: Fri, 18 Jun 2021 21:25:12 +0300 [thread overview]
Message-ID: <83im2bxc6v.fsf@gnu.org> (raw)
In-Reply-To: <87o8c3rwt8.fsf@gmx.net> (message from Stephen Berman on Fri, 18 Jun 2021 18:02:54 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: rpluim@gmail.com, 36767@debbugs.gnu.org, larsi@gnus.org,
> emacsuser@freemail.hu, juri@linkov.net
> Date: Fri, 18 Jun 2021 18:02:54 +0200
>
> > Thanks. But what I'd like to have is not a way of burying the Help
> > window, because I frequently need to consult it for quite some time.
> > What I'd like to have is a way of using its buttons without going to
> > that other window first. For example, I'd love a command, bound to a
> > key globally, that would display the source of the function in the
> > same window as the Help window, then allow me to go back to the Help
> > window.
>
> The command `help-view-source' that Lars recently added could probably
> help here, with some tweaking. It calls
> help-function-def--button-function, which calls pop-to-buffer with no
> ACTION argument, which results in the source buffer being displayed a
> different window than the *Help* buffer's window. So the first
> adjustment would be to add an optional ACTION argument. As far a
> returning from the source file to the *Help* buffer, the easiest way I
> can think of to do that is if the source file is visited in View mode:
> then `q' would bury its buffer, returning to *Help* (I think). Or would
> that not satisfy your use case?
I don't know, I'd have to try.
But surely, we could devise other methods to get back to the Help
buffer, ones that don't require View mode.
next prev parent reply other threads:[~2021-06-18 18:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 19:53 bug#36767: 26.1; request: add more quick keys to the *Help* buffer ndame
2019-07-22 20:49 ` Drew Adams
2019-07-28 0:10 ` Basil L. Contovounesios
2021-06-15 18:52 ` Lars Ingebrigtsen
2021-06-17 20:34 ` Juri Linkov
2021-06-18 6:02 ` Eli Zaretskii
2021-06-18 7:20 ` Robert Pluim
2021-06-18 10:58 ` Eli Zaretskii
2021-06-18 14:21 ` bug#36767: [External] : " Drew Adams
2021-06-18 14:32 ` Stephen Berman
2021-06-18 14:45 ` Eli Zaretskii
2021-06-18 16:02 ` Stephen Berman
2021-06-18 18:25 ` Eli Zaretskii [this message]
2021-06-19 9:08 ` martin rudalics
2021-06-19 9:27 ` Eli Zaretskii
2021-06-20 9:21 ` martin rudalics
2021-06-18 16:21 ` bug#36767: [External] : " Drew Adams
2021-06-18 14:12 ` Drew Adams
2021-06-18 19:14 ` Juri Linkov
2021-06-18 19:21 ` Eli Zaretskii
2021-06-19 23:15 ` Juri Linkov
[not found] ` <AM9PR09MB49779C8B93EFFB329EB8E5A596A29@AM9PR09MB4977.eurprd09.prod.outlook.com>
[not found] ` <83y27nvnb4.fsf@gnu.org>
[not found] ` <AM9PR09MB497767EDF180DE0C3EE15F4396A39@AM9PR09MB4977.eurprd09.prod.outlook.com>
[not found] ` <83ilyrvgda.fsf@gnu.org>
[not found] ` <AM9PR09MB497720FA603D3B7FC4D4739196A39@AM9PR09MB4977.eurprd09.prod.outlook.com>
2021-09-23 20:54 ` Lars Ingebrigtsen
2021-06-19 11:58 ` Lars Ingebrigtsen
2021-06-19 12:22 ` Eli Zaretskii
2021-06-19 23:15 ` Juri Linkov
[not found] ` <AM9PR09MB4977DAFB86D88A4714C1C64196A29@AM9PR09MB4977.eurprd09.prod.outlook.com>
[not found] ` <87pmt0qomh.fsf@gnus.org>
[not found] ` <AM9PR09MB4977CCFA194C77F1ADF0015C96A29@AM9PR09MB4977.eurprd09.prod.outlook.com>
2021-09-23 20:42 ` Lars Ingebrigtsen
2021-09-23 23:09 ` bug#36767: [External] : " Drew Adams
[not found] ` <AM9PR09MB49770845B0C1B7CBB331E68A96A39@AM9PR09MB4977.eurprd09.prod.outlook.com>
2021-09-23 20:52 ` Lars Ingebrigtsen
2021-09-26 9:11 ` martin rudalics
2021-09-26 9:40 ` Lars Ingebrigtsen
2021-09-26 9:55 ` Eli Zaretskii
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=83im2bxc6v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36767@debbugs.gnu.org \
--cc=emacsuser@freemail.hu \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.com \
--cc=stephen.berman@gmx.net \
/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).