timer after having read a key. It's not good for code reading
several keys in a loop, like an input method.
2000-12-04 Gerd Moellmann <gerd@gnu.org>
+ * keyboard.c (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.
+
* fileio.c (Finsert_file_contents): When VISIT is t, don't
record undo information for format-decode.
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)