# HG changeset patch # User Chong Yidong # Date 1237990711 0 # Node ID ca92073db2a9ba0feec593f0db6eeee9e9ab9b9b # Parent 03dcad98e4ebe7f801cb5665159557c73de76a98 (Focus Events): Most X window managers don't use focus-follows-mouse nowadays. diff -r 03dcad98e4eb -r ca92073db2a9 doc/lispref/commands.texi --- 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