# HG changeset patch
# User Martin Rudalics <rudalics@gmx.at>
# Date 1188461135 0
# Node ID e21dc4ec56d47effdb773897aa771d4f1cfbcd96
# Parent  150597026ddb44e619c176626153fa4f81ef80a3
(Command Loop Info): Advise against changing
most variables described here.  Explain new variable
last-repeatable-command.

diff -r 150597026ddb -r e21dc4ec56d4 lispref/commands.texi
--- a/lispref/commands.texi	Wed Aug 29 09:09:05 2007 +0000
+++ b/lispref/commands.texi	Thu Aug 30 08:05:35 2007 +0000
@@ -716,7 +716,9 @@
 @section Information from the Command Loop
 
 The editor command loop sets several Lisp variables to keep status
-records for itself and for commands that are run.
+records for itself and for commands that are run.  With the exception of
+@code{this-command} and @code{last-command} it's generally a bad idea to
+change any of these variables in a Lisp program.
 
 @defvar last-command
 This variable records the name of the previous command executed by the
@@ -736,6 +738,12 @@
 but never altered by Lisp programs.
 @end defvar
 
+@defvar last-repeatable-command
+This variable stores the most recently executed command that was not
+part of an input event.  This is the command @code{repeat} will try to
+repeat, @xref{Repeating,,, emacs, The GNU Emacs Manual}.
+@end defvar
+
 @defvar this-command
 @cindex current command
 This variable records the name of the command now being executed by