emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] emacs/doc/lispref commands.texi


From: Chong Yidong
Subject: [Emacs-diffs] emacs/doc/lispref commands.texi
Date: Wed, 25 Mar 2009 14:18:32 +0000

CVSROOT:        /sources/emacs
Module name:    emacs
Changes by:     Chong Yidong <cyd>      09/03/25 14:18:32

Modified files:
        doc/lispref    : commands.texi 

Log message:
        (Focus Events): Most X window managers don't use focus-follows-mouse
        nowadays.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/lispref/commands.texi?cvsroot=emacs&r1=1.16&r2=1.17

Patches:
Index: commands.texi
===================================================================
RCS file: /sources/emacs/emacs/doc/lispref/commands.texi,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- commands.texi       24 Mar 2009 17:08:49 -0000      1.16
+++ commands.texi       25 Mar 2009 14:18:31 -0000      1.17
@@ -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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]