From 4b0f717890dd0951bf68ebccada20f90580cdc30 Mon Sep 17 00:00:00 2001 From: Chong Yidong Date: Wed, 25 Mar 2009 14:18:31 +0000 Subject: [PATCH] (Focus Events): Most X window managers don't use focus-follows-mouse nowadays. --- doc/lispref/commands.texi | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi index e767574cecf..3eb339825cf 100644 --- a/doc/lispref/commands.texi +++ b/doc/lispref/commands.texi @@ -1567,13 +1567,12 @@ Focus events are represented in Lisp as lists that look like this: @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 -- 2.39.5