changeset 34174:f3a177a97f12

(Fread_key_sequence): Don't start the busy cursor timer after having read a key. It's not good for code reading several keys in a loop, like an input method.
author Gerd Moellmann <gerd@gnu.org>
date Mon, 04 Dec 2000 14:48:10 +0000
parents ddf7d535df2a
children d311c748a358
files src/keyboard.c
diffstat 1 files changed, 4 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/src/keyboard.c	Mon Dec 04 14:39:37 2000 +0000
+++ b/src/keyboard.c	Mon Dec 04 14:48:10 2000 +0000
@@ -8858,10 +8858,14 @@
 			 prompt, ! NILP (dont_downcase_last),
 			 ! NILP (can_return_switch_frame), 0);
 
+#if 0  /* The following is fine for code reading a key sequence and
+	  then proceeding with a lenghty compuation, but it's not good
+	  for code reading keys in a loop, like an input method.  */
 #ifdef HAVE_X_WINDOWS
   if (display_busy_cursor_p)
     start_busy_cursor ();
 #endif
+#endif
 
   if (i == -1)
     {