[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: change buffer in other frame, multiple monitors
From: |
Sam Halliday |
Subject: |
Re: change buffer in other frame, multiple monitors |
Date: |
Thu, 28 May 2015 04:22:23 -0700 (PDT) |
User-agent: |
G2/1.0 |
I've updated the below with the newer display-buffer-alist approach with
(setq display-buffer-alist
'((".*" display-buffer-reuse-window (reusable-frames . t))
(".*" display-buffer-pop-up-frame (inhibit-switch-frame . t))))
The reuse-window entry seems to reproduce the behaviour of the legacy setting I
was using.
I have added a display-buffer-pop-up-frame entry as per the documentation for
display-buffer but it seems to be ignored.
Is my syntax perhaps incorrect? Maybe there should only be one ".*"?
On Wednesday, 27 May 2015 15:16:27 UTC+1, Sam Halliday wrote:
> Hi all,
>
> I have a setup with multiple monitors and when using Emacs I have a frame in
> each monitor.
>
> I recently asked a question on this list and the solution was to set
>
> (setq-default display-buffer-reuse-frames t)
>
> so that 'next-error would not popup a new window (when the window was already
> open in a new frame).
>
> That worked great! I've recently been extending my use of basic emacs
> commands to include the commands under `C-x 5 ...` (i.e. the "do in the other
> frame" commands)
>
> However, when I type `C-x 5 b` and select a buffer name, I am expecting the
> buffer to be shown in the other frame. But instead, the buffer is opened in a
> new frame.
>
> It would appear that setting 'display-buffer-reuse-frames is not enough to
> force re-use of existing frames and this function is popping up a new one.
>
> Is there something else I must do to re-use frames? I note that
> display-buffer-reuse-frames is deprecated, but I'm not entirely sure how to
> migrate to the new world.
>
> Best regards,
> Sam