Opening special buffers "*Messages*" and "*scratch*" in new frames

Opening special buffers "*Messages*" and "*scratch*" in new frames

[Dr Rainer Woitok]

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)

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

Re: Opening special buffers "*Messages*" and "*scratch*" in new frames

[Philip Kaludercic]

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

Re: Opening special buffers "*Messages*" and "*scratch*" in new frames

[Joost Kremers]

On Tue, Jun 11 2024, Dr Rainer Woitok wrote:
>                ; (cons "^[*]\\(Messages\\|scratch\\)[*]"
>                ;       '(display-buffer-pop-up-frame
>                ;         (reusable-frames . t)))
[...]
> What did I do wrong?

I can't find anything wrong with it. If I try this in `emacs -Q`, it works as
expected: `C-h e` pops up a new frame, and so does `M-x pop-to-buffer RET
*scratch* RET`.


-- 
Joost Kremers
Life has its moments

Re: Opening special buffers "*Messages*" and "*scratch*" in new frames

[Dr Rainer Woitok]

Philip,

On Tue, 11 Jun 2024 09:46:34 +0000 you wrote:

> ...
> >          switch-to-buffer-obey-dislay-actions t)
>                                  ^ is this a typo ("dislay" vs
>                                  "display") in your message or in your
>                                  config?

OMG !! Thanks Philip.   Yes, this is (or better WAS) a typo in my confi-
guration file ... :-D

Sincerely,
  Rainer