Mercurial > emacs
changeset 102729:ca92073db2a9
(Focus Events): Most X window managers don't use focus-follows-mouse
nowadays.
| author | Chong Yidong <cyd@stupidchicken.com> |
|---|---|
| date | Wed, 25 Mar 2009 14:18:31 +0000 |
| parents | 03dcad98e4eb |
| children | 983c2b18a1c4 |
| files | doc/lispref/commands.texi |
| diffstat | 1 files changed, 6 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/lispref/commands.texi Wed Mar 25 14:17:57 2009 +0000 +++ b/doc/lispref/commands.texi Wed Mar 25 14:18:31 2009 +0000 @@ -1567,13 +1567,12 @@ @noindent where @var{new-frame} is the frame switched to. -Most X window managers are set up so that just moving the mouse into a -window is enough to set the focus there. Emacs appears to do this, -because it changes the cursor to solid in the new frame. However, there -is no need for the Lisp program to know about the focus change until -some other kind of input arrives. So Emacs generates a focus event only -when the user actually types a keyboard key or presses a mouse button in -the new frame; just moving the mouse between frames does not generate a +Some X window managers are set up so that just moving the mouse into a +window is enough to set the focus there. Usually, there is no need +for a Lisp program to know about the focus change until some other +kind of input arrives. Emacs generates a focus event only when the +user actually types a keyboard key or presses a mouse button in the +new frame; just moving the mouse between frames does not generate a focus event. A focus event in the middle of a key sequence would garble the