changeset 73097:86fa4c1273dd

(Command Loop Info): Explain how read-event affects this-command-keys.
author Richard M. Stallman <rms@gnu.org>
date Sun, 24 Sep 2006 20:33:29 +0000
parents 2f768f0aab61
children 28a1d231aeec
files lispref/commands.texi
diffstat 1 files changed, 7 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/lispref/commands.texi	Sun Sep 24 20:28:49 2006 +0000
+++ b/lispref/commands.texi	Sun Sep 24 20:33:29 2006 +0000
@@ -788,11 +788,13 @@
 @anchor{Definition of this-command-keys}
 This function returns a string or vector containing the key sequence
 that invoked the present command, plus any previous commands that
-generated the prefix argument for this command.  However, if the
-command has called @code{read-key-sequence}, it returns the last read
-key sequence.  @xref{Key Sequence Input}.  The value is a string if
-all events in the sequence were characters that fit in a string.
-@xref{Input Events}.
+generated the prefix argument for this command.  Any events read by the
+command using @code{read-event} without a timeout get tacked on to the end.
+
+However, if the command has called @code{read-key-sequence}, it
+returns the last read key sequence.  @xref{Key Sequence Input}.  The
+value is a string if all events in the sequence were characters that
+fit in a string.  @xref{Input Events}.
 
 @example
 @group