info-look.el bug

info-look.el bug

[Stephen Eglen]

Hi, 

I think I've found a little bug in info-look.el.  If anyone out there
regularly uses info-look.el, could they please check the following and
get back to me?

% emacs -q

In the *scratch* buffer, type "C-h S defun RET". The frame should divide
into two: the top window shows *scratch* and the bottom window shows
the definition of "defun" from the elisp *info*.

Still in the scratch buffer, type "C-h S setq RET".  This time the
*scratch* buffer disappears and is replaced by another window showing
*info* for setq; so now, both windows are showing an info node, but
the scratch buffer has gone.

I think this behaviour is wrong, and that if the *info* buffer is
already visible, it should not be viewed again in another window.  I
think have tracked down the problem to the call in info-lookup where
it calls Info-goto-node.  

I think this problem can be solved by using save-window-excursion, but
then on the second call to C-h S, the highlighting is not shown.
Anyone have a better idea of how to solve this?

Thanks, Stephen

Re: info-look.el bug

[Richard Stallman]

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)))))

Re: info-look.el bug

[Kevin Rodgers]

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

Re: info-look.el bug

[Richard Stallman]

    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.

In fact, that seems to be what the current code does.
So now I don't understand why the bug happens.

Re: info-look.el bug

[Kevin Rodgers]

Richard Stallman wrote:
 >     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.
 >
 > In fact, that seems to be what the current code does.
 > So now I don't understand why the bug happens.

Although the original bug report was sent to the emacs-devel@gnu.org
mailing list, it was apparently about Emacs 21.3 (not CVS Emacs):

	From: Stephen Eglen <stephen@inf.ed.ac.uk>
	To: emacs-devel@gnu.org
	Subject: info-look.el bug
	Date: Sun, 1 Feb 2004 14:48:31 +0000
	Message-ID: <16413.4543.492252.351095@bushmills.inf.ed.ac.uk>
	X-Mailer: VM 7.17 under Emacs 21.3.2

I confirmed that the bug is present in Emacs 21.3, so I sent a patch to
the gnu.emacs.bug newsgroup.

-- 
Kevin Rodgers