summaryrefslogtreecommitdiff
path: root/doc/lispref/commands.texi
diff options
context:
space:
mode:
authorChong Yidong <cyd@stupidchicken.com>2009-03-25 14:18:31 +0000
committerChong Yidong <cyd@stupidchicken.com>2009-03-25 14:18:31 +0000
commit4b0f717890dd0951bf68ebccada20f90580cdc30 (patch)
treefed6fd5f6bda20c57bbf0802324cab728d90c048 /doc/lispref/commands.texi
parent48bab3d600d848bfc2fce93287fedc0f4d410fff (diff)
downloademacs-4b0f717890dd0951bf68ebccada20f90580cdc30.tar.gz
(Focus Events): Most X window managers don't use focus-follows-mouse
nowadays.
Diffstat (limited to 'doc/lispref/commands.texi')
-rw-r--r--doc/lispref/commands.texi13
1 files 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