[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: windmove and the minibuffer

From: Alex Schroeder
Subject: Re: windmove and the minibuffer
Date: Sun, 01 Jun 2003 10:44:52 +0200
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

Luc Teirlinck <address@hidden> writes:

>        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.
> Alex, what return value do you get for the above form, in the above
> situation?

Using the above instructions, I get:

(0 . 0)

Then I do
M-x windmove-default-keybindings
C-x C-f

So currently the minibuffer is active, but I am in *scratch*.
The above sexp still returns (0 . 0).
S-down still does not go back to the minibuffer.

> Also which return values do you get, in that same
> situation, for:
> (window-at 0 15)

#<window 3 on *scratch*>

> (window-at 1 (window-height))

#<window 3 on *scratch*>

> (window-at 0 (window-height))

#<window 3 on *scratch*>

> (window-at 1 (1+ (window-height)))

#<window 4 on  *Minibuf-0*>

The result are just the same when I have an active minibuffer.

> It are mainly the window-at values that are relevant to Alex's
> problem, but the coordinates-in-window-p problem is closely related.
> I use RedHat7.2.

I use Debian testing/unstable


"GNU Emacs (i686-pc-linux-gnu, X toolkit)
 of 2003-05-24 on confusibombus"

system-configuration           "i686-pc-linux-gnu"
system-configuration-options   ""


reply via email to

[Prev in Thread] Current Thread [Next in Thread]