From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: change buffer in other frame, multiple monitors
Date: Thu, 28 May 2015 16:25:06 +0200 [thread overview]
Message-ID: <874mmwpynx.fsf@web.de> (raw)
In-Reply-To: b1c18da7-8dbc-42a7-9680-d5c6e4edcfb1@googlegroups.com
Sam Halliday <sam.halliday@gmail.com> writes:
> (setq display-buffer--other-frame-action
> '((display-buffer-reuse-window display-buffer-pop-up-frame)
> (reusable-frames . t) (inhibit-same-window . t)))
That makes the thing reuse a frame only when there is a window already
displaying the buffer - see doc of `display-buffer-reuse-window'.
This is seemingly not what you want. What do you want instead: that a
random window in a random frame is selected and forced to display the
buffer?
Michael.
next prev parent reply other threads:[~2015-05-28 14:25 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
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 [this message]
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=874mmwpynx.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).