From: Chong Yidong <cyd@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: 4271@debbugs.gnu.org
Subject: bug#4271: 23.1; pop-to-buffer -vs- multiple terminals
Date: Wed, 20 Jun 2012 02:03:22 -0400 [thread overview]
Message-ID: <yyxehpa7c5x.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m3fxbex9qf.fsf@fleche.redhat.com>
> I ran (pop-to-buffer "*vc-diff*") and this did not show the buffer. I
> think that this should ignore frames on other terminals when
> determining whether a buffer is visible.
The pop-to-buffer code has been completely rewritten since this bug was
filed, and AFAICT the new code will not reuse a window on a different
terminal unless you specifically force it to. Closing.
prev parent reply other threads:[~2012-06-20 6:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 2:37 bug#4271: 23.1; pop-to-buffer -vs- multiple terminals Tom Tromey
2009-08-27 5:17 ` Stefan Monnier
2009-08-27 5:52 ` martin rudalics
2012-06-20 6:03 ` Chong Yidong [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=yyxehpa7c5x.fsf@fencepost.gnu.org \
--to=cyd@gnu.org \
--cc=4271@debbugs.gnu.org \
--cc=tromey@redhat.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).