From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: info-look.el bug
Date: Fri, 06 Feb 2004 13:30:05 -0700 [thread overview]
Message-ID: <4023F94D.5080307@yahoo.com> (raw)
In-Reply-To: E1AokrR-0007EN-OM@fencepost.gnu.org
Richard Stallman wrote:
> When you want to switch to a buffer and let display-buffer choose
> where it should appear, you use pop-to-buffer. I think it is a bug
> for switch-to-buffer-other-window to obey same-window-buffer-names
> or same-window-regexps. So I think this change is called for.
>
> However, it may be that some existing calls to
> switch-to-buffer-other-window would need to be changed to use
> pop-to-buffer.
I agree with your change, but I don't think it goes far enough. Here's
what pop-to-buffer's doc string says:
| If optional second arg OTHER-WINDOW is non-nil, insist on finding another
| window even if BUFFER is already visible in the selected window.
To me, that means that no calls to (pop-to-buffer BUFFER t ...) should
obey same-window-buffer-names or -regexps, not just those in
switch-to-buffer-other-window and -frame. And so I think the job of
temporarily binding same-window-buffer-names and -regexps should be done
in pop-to-buffer:
(let ((same-window-buffer-names (if other-window
nil
same-window-buffer-names))
(same-window-regexps (if other-window
nil
same-window-regexps)))
...)
Unfortunately, pop-to-buffer is implemented in C and I don't know how to
write that fragment in C.
--
Kevin Rodgers
next prev parent reply other threads:[~2004-02-06 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 14:48 info-look.el bug Stephen Eglen
[not found] ` <mailman.1759.1075771606.928.bug-gnu-emacs@gnu.org>
[not found] ` <401FD49A.5010506@yahoo.com>
2004-02-05 14:52 ` Richard Stallman
2004-02-06 20:30 ` Kevin Rodgers [this message]
2004-02-07 19:34 ` Richard Stallman
2004-02-09 20:34 ` Kevin Rodgers
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=4023F94D.5080307@yahoo.com \
--to=ihs_4664@yahoo.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).