From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 72769@debbugs.gnu.org
Subject: bug#72769: 31.0.50; info-pop-to-buffer should respect display-buffer-alist
Date: Fri, 23 Aug 2024 15:32:52 +0300 [thread overview]
Message-ID: <868qwnqv0r.fsf@gnu.org> (raw)
In-Reply-To: <8734mvd7fv.fsf@> (message from Björn Bidar on Fri, 23 Aug 2024 10:28:20 +0300)
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: 72769@debbugs.gnu.org
> Date: Fri, 23 Aug 2024 10:28:20 +0300
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I'd like to ask the opposite: are there any reasons to change the
> > current behavior? This command existed for quite some time, and no
> > one has complained about its behavior so far. Consistency by itself
> > is not a reason good enough to make such changes, so are there other
> > reasons?
> >
>
> The behaviour on how and where info is opened is not customizable as
> opposed to for example the help or man where dispaly-buffer-alist is
> respected.
> While it wouldn't help existing users I think would help newer users.
But the main command to show Info manuals is not info-display-manual,
it's "M-x info".
> 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?
next prev parent reply other threads:[~2024-08-23 12:32 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 [this message]
2024-08-23 16:43 ` Kévin Le Gouguec
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868qwnqv0r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72769@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.