[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: windmove and the minibuffer
From: |
Luc Teirlinck |
Subject: |
Re: windmove and the minibuffer |
Date: |
Wed, 28 May 2003 15:11:39 -0500 (CDT) |
I am now convinced that the bug is not in windmove, but in `window-at'
and `coordinates-in-window-p'.
Indeed, the documentation of `window-at' is rather ambiguous but doing
C-h f coordinates-in-window-p, we see:
(0 . 0) denotes the character in the upper left corner of the
frame.
This seems to clearly imply that after:
emacs-21.3.50 -q --eval "(blink-cursor-mode 0)" &
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. What
happens on MS Windows?
Sincerely,
Luc.
- windmove and the minibuffer, Alex Schroeder, 2003/05/26
- Re: windmove and the minibuffer, Luc Teirlinck, 2003/05/27
- Re: windmove and the minibuffer, Juanma Barranquero, 2003/05/28
- Re: windmove and the minibuffer, Richard Stallman, 2003/05/31
- Re: windmove and the minibuffer, Luc Teirlinck, 2003/05/31
- Re: windmove and the minibuffer, Robert J. Chassell, 2003/05/31
- Re: windmove and the minibuffer, Luc Teirlinck, 2003/05/31
- Re: windmove and the minibuffer, Juanma Barranquero, 2003/05/28
- Re: windmove and the minibuffer, Luc Teirlinck, 2003/05/28