all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 9532@debbugs.gnu.org
Subject: bug#9532: 24.0.50; `special-display-regexps' is no longer respected
Date: Wed, 21 Sep 2011 23:37:06 -0400	[thread overview]
Message-ID: <87zkhxnt7h.fsf@stupidchicken.com> (raw)
In-Reply-To: <8739fp6z4h.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 21 Sep 2011 23:21:18 -0400")

Chong Yidong <cyd@stupidchicken.com> writes:

> 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.
>
> If you agree, I'd implement the behavior by adding a new value for
> s-t-b's FORCE-SAME-WINDOW argument, `try', which would be the default
> for interactive calls.  That would mean to first try displaying in the
> current selected window directly instead of going through p-t-b.

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.

There are only about 9 uses of the same-window-regexps + display-buffer
trick which would be changed to use pop-to-buffer-same-window, compared
to hundreds of users of switch-to-buffer.  So unintended consequences
would be much less likely.





  reply	other threads:[~2011-09-22  3:37 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 [this message]
2011-09-22 12:29                     ` Stefan Monnier
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=87zkhxnt7h.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=9532@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.