unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: 72769@debbugs.gnu.org
Cc: bjorn.bidar@thaodan.de, eliz@gnu.org, kevin.legouguec@gmail.com
Subject: bug#72769: 31.0.50; info-pop-to-buffer should respect display-buffer-alist
Date: Sun, 25 Aug 2024 09:48:06 +0300	[thread overview]
Message-ID: <86jzg5m72x.fsf@mail.linkov.net> (raw)
In-Reply-To: <87plpyaznd.fsf@> ("Björn Bidar via \"Bug reports for GNU Emacs, the Swiss army knife of text editors\""'s message of "Sat, 24 Aug 2024 15:11:50 +0300")

>> 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.
>
> I have exactly the same workflow in the situation you describe.
> I also create a separate frame each time I open new manual, but if
> info would follow the display-buffer-alist rules I wouldn't have to do
> that my self and the frame would be closed when I close the manual.

Please show your display-buffer-alist configuration where
Info doesn't follow the display-buffer-alist rules.
I see that 'C-h R' follows these rules in e.g.:

  (add-to-list 'display-buffer-alist
               '("\\*info\\*"
                 display-buffer-pop-up-window))





  parent reply	other threads:[~2024-08-25  6:48 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 [this message]
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=86jzg5m72x.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=72769@debbugs.gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --cc=eliz@gnu.org \
    --cc=kevin.legouguec@gmail.com \
    /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).