From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Chong Yidong <cyd@gnu.org>
Cc: 10144@debbugs.gnu.org
Subject: bug#10144: 24.0.91; `pop-up-frames' with dedicated windows is broken: `C-x C-f'
Date: Tue, 29 Nov 2011 09:01:33 -0500 [thread overview]
Message-ID: <jwvty5n81zn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ty5nfqj1.fsf@gnu.org> (Chong Yidong's message of "Tue, 29 Nov 2011 13:26:10 +0800")
>> I reverted the code to a behavior closer to Emacs-23's behavior.
> Using set-window-buffer has the disadvantage that now switch-to-buffer
> can't be affected by display-buffer-alist (except for the
> dedicated/minibuffer window case where pop-to-buffer is used).
> Why not use pop-to-buffer-same-window there, rather than
> set-window-buffer?
It's a safer change. Callers can use pop-to-buffer-same-window if they
like that better. In the absence of display-buffer-alist there's also
a difference of behavior for softly-dedicated windows where
set-window-buffer will undedicate the window whereas
pop-to-buffer-same-window will use another window.
Stefan
next prev parent reply other threads:[~2011-11-29 14:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 18:27 bug#10144: 24.0.91; `pop-up-frames' with dedicated windows is broken: `C-x C-f' Drew Adams
2011-11-26 19:14 ` martin rudalics
2011-11-26 19:26 ` Drew Adams
2011-11-27 10:41 ` martin rudalics
2011-11-27 14:17 ` Drew Adams
2011-11-28 4:37 ` Stefan Monnier
2011-11-28 13:33 ` martin rudalics
2011-11-28 16:56 ` Stefan Monnier
2011-11-28 17:01 ` Drew Adams
2011-11-28 19:40 ` Stefan Monnier
2011-11-29 10:48 ` martin rudalics
2011-11-29 14:03 ` Stefan Monnier
2011-11-29 10:48 ` martin rudalics
2011-11-29 14:04 ` Stefan Monnier
2011-11-28 15:30 ` Drew Adams
2011-11-28 17:07 ` Stefan Monnier
2011-11-28 17:25 ` Drew Adams
2011-11-28 19:45 ` Stefan Monnier
2011-11-29 5:26 ` Chong Yidong
2011-11-29 14:01 ` Stefan Monnier [this message]
2011-11-30 18:22 ` Drew Adams
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=jwvty5n81zn.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=10144@debbugs.gnu.org \
--cc=cyd@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.
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).