From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: info-look.el bug
Date: Thu, 05 Feb 2004 09:52:09 -0500 [thread overview]
Message-ID: <E1AokrR-0007EN-OM@fencepost.gnu.org> (raw)
In-Reply-To: <401FD49A.5010506@yahoo.com> (message from Kevin Rodgers on Tue, 03 Feb 2004 10:04:26 -0700)
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.
*** files.el.~1.677.~ Fri Jan 16 12:19:44 2004
--- files.el Thu Feb 5 01:07:44 2004
***************
*** 850,856 ****
This uses the function `display-buffer' as a subroutine; see its
documentation for additional customization information."
(interactive "BSwitch to buffer in other window: ")
! (let ((pop-up-windows t))
(pop-to-buffer buffer t norecord)))
(defun switch-to-buffer-other-frame (buffer &optional norecord)
--- 850,857 ----
This uses the function `display-buffer' as a subroutine; see its
documentation for additional customization information."
(interactive "BSwitch to buffer in other window: ")
! (let ((pop-up-windows t)
! same-window-buffer-names same-window-regexps)
(pop-to-buffer buffer t norecord)))
(defun switch-to-buffer-other-frame (buffer &optional norecord)
***************
*** 861,867 ****
This uses the function `display-buffer' as a subroutine; see its
documentation for additional customization information."
(interactive "BSwitch to buffer in other frame: ")
! (let ((pop-up-frames t))
(pop-to-buffer buffer t norecord)
(raise-frame (window-frame (selected-window)))))
--- 862,869 ----
This uses the function `display-buffer' as a subroutine; see its
documentation for additional customization information."
(interactive "BSwitch to buffer in other frame: ")
! (let ((pop-up-frames t)
! same-window-buffer-names same-window-regexps)
(pop-to-buffer buffer t norecord)
(raise-frame (window-frame (selected-window)))))
next prev parent reply other threads:[~2004-02-05 14:52 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 [this message]
2004-02-06 20:30 ` Kevin Rodgers
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=E1AokrR-0007EN-OM@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).