From: Philip Kaludercic <philipk@posteo.net>
To: Dr Rainer Woitok <rainer.woitok@gmail.com>
Cc: Help-Gnu-Emacs@Gnu.Org
Subject: Re: Opening special buffers "*Messages*" and "*scratch*" in new frames
Date: Tue, 11 Jun 2024 09:46:34 +0000 [thread overview]
Message-ID: <87v82fyfph.fsf@posteo.net> (raw)
In-Reply-To: <66681903.050a0220.6da3d.41e7@mx.google.com> (Rainer Woitok's message of "Tue, 11 Jun 2024 11:29:37 +0200")
Dr Rainer Woitok <rainer.woitok@gmail.com> writes:
> Greetings,
>
> a few weeks back there was some discussion on this list about opening
> special buffers in new frames. This motivated me to add the following
> lines to my Emacs configuration file:
>
> (setq display-buffer-alist
> (list (cons "\\(^ [*]\\)\\|\\(^[*]Completions[*]\\)"
> display-buffer--same-window-action)
>
> ; (cons "^[*]\\(Messages\\|scratch\\)[*]"
> ; '(display-buffer-pop-up-frame
> ; (reusable-frames . t)))
>
> (cons "^[*]"
> '((display-buffer-reuse-window
> display-buffer-pop-up-frame)
> (reusable-frames . t )
> (inhibit-same-window . nil))))
>
> switch-to-buffer-in-dedicated-window 'pop
> switch-to-buffer-obey-dislay-actions t)
^ is this a typo ("dislay" vs
"display") in your message or in your
config?
>
> However, regardless of whether or not the three commented-out lines a-
> bove were uncommented, buffers "*Messages*" and "*scratch*" were always
> opened in the current window of the current frame.
>
> But explicitly running "C-x 5 b *Messages*" or "C-x 5 b *scratch*" work
> as expected.
>
> What did I do wrong?
>
> Sincerely,
> Rainer
>
>
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-06-11 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 9:29 Opening special buffers "*Messages*" and "*scratch*" in new frames Dr Rainer Woitok
2024-06-11 9:46 ` Philip Kaludercic [this message]
2024-06-11 10:17 ` Dr Rainer Woitok
2024-06-11 10:08 ` Joost Kremers
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=87v82fyfph.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=Help-Gnu-Emacs@Gnu.Org \
--cc=rainer.woitok@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.
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).