Re: windmove and the minibuffer

[Robert J. Chassell]

Luc Teirlinck <address@hidden> asked about a bug concerning
windmove and the minibuffer.

I see the bug.  I invoked Emacs like this:

  /usr/local/bin/emacs -q --no-site-file --eval '(blink-cursor-mode 0)'

Then:
          M-x scroll-bar-mode
          M-x fringe-mode
          M-x tool-bar-mode
          M-x menu-bar-mode

          (coordinates-in-window-p '(0 . 0) (selected-window))

          should not return nil.  But it does, at least on GNU/Linux.

RMS writes:

      It returned (0 . 0) when I tried it.

Luc Teirlinck <address@hidden> writes:

   Still returns nil for me in freshly updated CVS Emacs. 

And I got nil, too, in freshly updated CVS Emacs.

Today's CVS snapshot, Sun, 2003 May 31 20:36 UTC
GNU Emacs 21.3.50.68 (i686-pc-linux-gnu, X toolkit)
with a Linux kernel
started with:

  /usr/local/bin/emacs -q --no-site-file --eval '(blink-cursor-mode 0)'


Luc Teirlinck <address@hidden> asks:

   Can you reproduce Alex's original bug:

   Run emacs -q

(require 'windmove)

   M-x windmove-default-keybindings  (After loading windmove, of course.)
   C-x C-f (you should be in the minibuffer, now)
   S-up (you should be in *scratch*, now)
   S-down (I am still in *scratch*, even though I want to be in the
   minibuffer)

Yes, I just reproduced that exactly.

   ... which return values do you get ....

Here they are:

   (window-at 0 15)nil
   (window-at 1 (window-height))#<window 3 on *scratch*>
   (window-at 0 (window-height))nil
   (window-at 1 (1+ (window-height)))#<window 4 on  *Minibuf-1*>

   (emacs-version)"GNU Emacs 21.3.50.68 (i686-pc-linux-gnu, X toolkit)
 of 2003-05-31 on benthic.rattlesnake.com"

-- 
    Robert J. Chassell                         Rattlesnake Enterprises
    http://www.rattlesnake.com                  GnuPG Key ID: 004B4AC8
    http://www.teak.cc                             address@hidden