From: Yuri Khan <yuri.v.khan@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: change buffer in other frame, multiple monitors
Date: Thu, 28 May 2015 21:03:16 +0600 [thread overview]
Message-ID: <CAP_d_8W0v=iKuFn-hRdjX3Y2bjz6_mircnUhZJOZ8mmte_hvbg@mail.gmail.com> (raw)
In-Reply-To: <874mmwpynx.fsf@web.de>
On Thu, May 28, 2015 at 8:25 PM, Michael Heerdegen
<michael_heerdegen@web.de> wrote:
> What do you want instead: that a
> random window in a random frame is selected and forced to display the
> buffer?
I think the implicit assumption is that there exists a unique frame
other than the current one, and that it contains a single window.
I find myself in such a setup quite often, although my normal workflow
is then to switch to the other frame (using windmove + framemove) and
then select whatever buffer I need in that frame.
prev parent reply other threads:[~2015-05-28 15:03 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
2015-05-28 15:03 ` Yuri Khan [this message]
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='CAP_d_8W0v=iKuFn-hRdjX3Y2bjz6_mircnUhZJOZ8mmte_hvbg@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).