From: Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "bjorn.bidar@thaodan.de" <bjorn.bidar@thaodan.de>,
"72769@debbugs.gnu.org" <72769@debbugs.gnu.org>
Subject: bug#72769: 31.0.50; info-pop-to-buffer should respect display-buffer-alist
Date: Fri, 23 Aug 2024 16:39:48 +0000 [thread overview]
Message-ID: <DS7PR10MB5232A20A7FFD7C61DEE110A6F3882@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86msl3p6f1.fsf@gnu.org>
> > > 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.
> >
> > Just give the Info buffer a dedicated window.
>
> Is there any other way?
No doubt. That's just the way I do it.
> In my sessions, all Info manuals are shown in
> a separate frame, which is only used for that purpose.
Me too, but if I clone an Info buffer I want it too in another separate frame.
next prev parent reply other threads:[~2024-08-23 16:39 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
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 [this message]
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=DS7PR10MB5232A20A7FFD7C61DEE110A6F3882@DS7PR10MB5232.namprd10.prod.outlook.com \
--to=bug-gnu-emacs@gnu.org \
--cc=72769@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=drew.adams@oracle.com \
--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 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.