From 823fb6e2f3025ee60ec9ba3a6da397f302b3ec1f Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Sun, 24 Sep 2006 20:33:29 +0000 Subject: [PATCH] (Command Loop Info): Explain how read-event affects this-command-keys. --- lispref/commands.texi | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/lispref/commands.texi b/lispref/commands.texi index 514b55205a1..e27488964d0 100644 --- a/lispref/commands.texi +++ b/lispref/commands.texi @@ -788,11 +788,13 @@ was specified to run but remapped into another command. @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 -- 2.39.2