From: Sam Halliday <sam.halliday@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: change buffer in other frame, multiple monitors
Date: Thu, 28 May 2015 04:22:23 -0700 (PDT) [thread overview]
Message-ID: <c8b44262-cc2f-4e58-8f96-ea6828feed14@googlegroups.com> (raw)
In-Reply-To: <06e2726d-4e00-4fb6-bfa3-0f272a652796@googlegroups.com>
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
next prev parent reply other threads:[~2015-05-28 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 14:16 change buffer in other frame, multiple monitors Sam Halliday
2015-05-28 11:22 ` Sam Halliday [this message]
2015-05-28 14:02 ` Sam Halliday
2015-05-28 14:16 ` Sam Halliday
2015-05-28 14:26 ` Sam Halliday
2015-05-28 14:25 ` Michael Heerdegen
2015-05-28 15:03 ` Yuri Khan
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=c8b44262-cc2f-4e58-8f96-ea6828feed14@googlegroups.com \
--to=sam.halliday@gmail.com \
--cc=help-gnu-emacs@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.
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).