From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 9532@debbugs.gnu.org
Subject: bug#9532: 24.0.50; `special-display-regexps' is no longer respected
Date: Thu, 22 Sep 2011 08:29:18 -0400 [thread overview]
Message-ID: <jwv39fog4fi.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87zkhxnt7h.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 21 Sep 2011 23:37:06 -0400")
>> So, you agree to the incompatibility for the non-interactive case? That
>> is to say, a non-interactive call to switch-to-buffer (and ONLY a
>> non-interactive call) will now trigger special display. Previously, in
>> Emacs 23, it would use the selected window.
Yes.
> It just occurred to me that it would be safer to leave switch-to-buffer
> unchanged, and instead reinstate pop-to-buffer-same-window specifically
> for the callers in question, i.e. the callers who used the
> same-window-regexps/display-buffer trick. pop-to-buffer-same-window
> would raise a special window for special buffers, instead of using the
> selected window; s-t-b would use the selected window, as in Emacs 23.
It would also be a change in behavior since same-window-* took
precedence over special-display-*. But it would be a good change: users
like Drew (and myself) had to set same-window-* to nil to let
special-display-* do its job.
So I agree those callers who used same-window-* should be changed to
obey special-display-*, as for whether callers of switch-to-buffer
should also obey special-display-* (and/or display-buffer-alist) I don't
know for sure.
Basically w.r.t "same-window behavior" we have 3 options:
1- never touch another window.
2- obey special-display-* and display-buffer-alist.
3- use the selected window if at all possible, but fallback to
pop-to-buffer instead of signalling an error.
The third is the current behavior of interactive uses of switch-to-buffer.
The second is the behavior we want for former users of same-window-*.
The third is the behavior that corresponds to Emacs-23's switch-to-buffer.
We could shoehorn this into the `force-same-window' argument of
switch-to-buffer, but I'm not convinced that the difference between
options 2 and 3 is worth the trouble.
Stefan
next prev parent reply other threads:[~2011-09-22 12:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 14:55 bug#9532: 24.0.50; `special-display-regexps' is no longer respected Drew Adams
2011-09-18 15:13 ` Chong Yidong
2011-09-18 17:33 ` Drew Adams
2011-09-20 21:52 ` Drew Adams
2011-09-21 1:38 ` Stefan Monnier
2011-09-21 16:06 ` Chong Yidong
2011-09-21 16:30 ` Drew Adams
2011-09-21 17:01 ` Chong Yidong
2011-09-21 17:11 ` Drew Adams
2011-10-02 18:44 ` Drew Adams
2011-10-19 18:51 ` Drew Adams
2011-10-31 15:24 ` Drew Adams
2011-11-05 21:17 ` Drew Adams
2011-11-08 2:59 ` Stefan Monnier
2011-11-08 5:39 ` Drew Adams
2011-11-08 6:25 ` Eli Zaretskii
2011-11-08 6:47 ` Drew Adams
2011-11-08 13:26 ` Stefan Monnier
2011-11-08 17:37 ` Drew Adams
2011-11-08 19:28 ` Stefan Monnier
2011-09-21 17:59 ` Stefan Monnier
2011-09-21 18:30 ` Chong Yidong
2011-09-22 1:16 ` Stefan Monnier
2011-09-22 3:21 ` Chong Yidong
2011-09-22 3:37 ` Chong Yidong
2011-09-22 12:29 ` Stefan Monnier [this message]
2011-09-22 16:15 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv39fog4fi.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9532@debbugs.gnu.org \
--cc=cyd@stupidchicken.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.