unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 9532@debbugs.gnu.org
Subject: bug#9532: 24.0.50; `special-display-regexps' is no longer respected
Date: Wed, 21 Sep 2011 13:01:08 -0400	[thread overview]
Message-ID: <877h51n82z.fsf@stupidchicken.com> (raw)
In-Reply-To: <208166A8F7EF4681B76EADADCA39822C@us.oracle.com> (Drew Adams's message of "Wed, 21 Sep 2011 09:30:46 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

>> OTOH, I don't see an easy way to handle all the backward
>> compatibility exceptions in this case.
>
> FWIW, Martin's code worked fine in this regard.
> ...
> Perhaps look to Martin's code for an answer?  Even if you decide not
> to do everything the same way he did it, perhaps for things like this
> his code can help guide you.  Dunno.

I don't know why you seem to think that there is some great mystery
here.  The issue is quite clear: how to handle the transition away from
same-window-regexps in commands like `info'.

The current code, AFAICT, also "works fine" if you change info back to
using pop-to-buffer + same-window-regexps.

I am coming to the conclusion that there is no good way to handle the
change "smoothly", in the sense of having an intermediate stage where
internal Emacs code (outside of window.el) transitions away from using
same-window-regexps.  That is to say, until we are prepared to outright
change the behavior of commands like `info' wrt certain combinations of
same-window-* and special-window-* settings, we have to continue using
same-window-regexps in those source files.

Stefan, any thoughts?





  reply	other threads:[~2011-09-21 17:01 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 [this message]
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
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

  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=877h51n82z.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=9532@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).