all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: jmbarranquero@laley.wke.es
Subject: Re: windmove and the minibuffer
Date: Sun, 1 Jun 2003 08:36:22 -0500 (CDT)	[thread overview]
Message-ID: <200306011336.h51DaMk22696@eel.dms.auburn.edu> (raw)
In-Reply-To: <87u1bab30b.fsf@gnu.org> (message from Alex Schroeder on Sun, 01 Jun 2003 10:44:52 +0200)

So depending on "something" we actually can get not two, but three
different window-at behaviors.  It might be difficult to figure out
what the "something" is without studying the C code.  I know C, but,
at present, I am not really familiar at all with Emacs' C code, just
with its Elisp code.

   S-down still does not go back to the minibuffer.
   Hm.

I do understand that, given:

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

   #<window 3 on *scratch*>

With point at the beginning of the scratch buffer, these are the
coordinates that `windmove-find-other-window' passes to window-at.
Hence, you stay in *scratch* (without error message).  On my system,
the expression returns nil, so I get an error message (and also stay
in scratch).

For Juanma the expression returns:

 #<window 4 on  *Minibuf-0*>

So he goes to the minibiuffer.

If one could fix the window-at problem, the windmove problem would
automatically disappear.  This is not a bug in windmove.el.

Sincerely,

Luc.

  parent reply	other threads:[~2003-06-01 13:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 17:52 windmove and the minibuffer Alex Schroeder
2003-05-27  8:03 ` Juanma Barranquero
2003-05-27 17:25   ` Alex Schroeder
2003-05-27 21:59     ` Juanma Barranquero
2003-05-27 23:04       ` Luc Teirlinck
2003-05-28  2:16 ` Luc Teirlinck
2003-05-28  7:00   ` Juanma Barranquero
2003-05-28 19:27     ` Luc Teirlinck
2003-05-28 20:11       ` Luc Teirlinck
2003-05-28 22:41         ` Juanma Barranquero
2003-05-28 22:55           ` Luc Teirlinck
2003-05-31 19:52         ` Richard Stallman
2003-05-31 23:16           ` Luc Teirlinck
2003-06-01  0:10             ` Robert J. Chassell
2003-06-01  0:46               ` Luc Teirlinck
2003-06-01  8:44             ` Alex Schroeder
2003-06-01 12:04               ` Robert J. Chassell
2003-06-01 12:15                 ` David Kastrup
2003-06-01 16:29                   ` { SPAM 2 }::Re: " Luc Teirlinck
2003-06-01 13:36               ` Luc Teirlinck [this message]
2003-06-01 14:21               ` Luc Teirlinck
2003-06-01 14:49                 ` Luc Teirlinck
2003-06-01 15:46                 ` Luc Teirlinck
2003-06-01 16:05                   ` Luc Teirlinck
2003-06-01 17:30                   ` Alex Schroeder
2003-06-02 11:15             ` Richard Stallman
2003-05-28 23:05       ` Juanma Barranquero
2003-05-28 23:25         ` Luc Teirlinck
     [not found] <E19KknO-0004NB-Qx@monty-python.gnu.org>
2003-05-28  6:11 ` Lars Hansen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200306011336.h51DaMk22696@eel.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=jmbarranquero@laley.wke.es \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.