From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Björn Bidar" <bjorn.bidar@thaodan.de>, 72769@debbugs.gnu.org
Subject: bug#72769: 31.0.50; info-pop-to-buffer should respect display-buffer-alist
Date: Fri, 23 Aug 2024 18:43:51 +0200 [thread overview]
Message-ID: <87wmk7nq9k.fsf@gmail.com> (raw)
In-Reply-To: <868qwnqv0r.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 23 Aug 2024 15:32:52 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> But the main command to show Info manuals is not info-display-manual,
> it's "M-x info".
(FWIW, I invoke info-display-manual several times a day; I like that it
prompts for the manual to open, with completion on names for manuals
installed in the standard paths)
>> For my own personal use the issue is that I don't like when info doesn't
>> open in a new window so that I don't have open a frame/window to keep
>> looking at the existing thing I was doing at that time e.g. programming.
>
> The question is why do you need/want that when you invoke this
> particular command? For that matter, under what circumstances do you
> invoke this command to begin with?
Selected window shows code that I want to keep looking at: I invoke
C-x 4 4 C-h R
to start browsing the manual of interest, keeping the code visible.
Selected window shows documentation I am done reading for now (a help
buffer, a manpage, another info manual): I invoke
C-x 4 1 C-h R
to start browsing another manual, clobbering my "reference
documentation" window.
(This is while working on languages that have poor Info integration, of
course; C-h S serves me better in e.g. Elisp or Make code)
FWIW I am happy with the C-x 4 [14] status quo, but it makes sense to me
that some folks would have "info usage patterns" similar to mine, while
preferring to use display-buffer-alist rules.
next prev parent reply other threads:[~2024-08-23 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wmk7er9q.fsf@>
2024-08-23 6:58 ` bug#72769: 31.0.50; info-pop-to-buffer should respect display-buffer-alist Eli Zaretskii
2024-08-23 7:28 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <8734mvd7fv.fsf@>
2024-08-23 12:32 ` Eli Zaretskii
2024-08-23 16:43 ` Kévin Le Gouguec [this message]
2024-08-24 12:11 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87plpyaznd.fsf@>
2024-08-24 12:53 ` Eli Zaretskii
2024-08-25 6:48 ` Juri Linkov
2024-08-24 12:03 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-23 15:02 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-23 16:09 ` Eli Zaretskii
2024-08-23 16:39 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-23 5:34 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87wmk7nq9k.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=72769@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
/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).