* lispref/commands.texi (Defining Commands): List interactive-only values.

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index d911a812d30902cfb9cc2a2f2f09b7711df8a3e3..1e57d4f0db2bd9bd1a78309dad0df70e7ed56b79 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2014-03-22  Glenn Morris  <rgm@gnu.org>
+
+       * commands.texi (Defining Commands): List interactive-only values.
+
 2014-03-22  Eli Zaretskii  <eliz@gnu.org>
 
        * functions.texi (Core Advising Primitives): Fix cross-reference

diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 198926a9a6ab7fa29ed4cf85454ae560eaf73f6e..998f76cc3d0b13b6932b669eae43d1dcf5ba2954 100644 (file)
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -126,7 +126,11 @@ form in the function body itself.  This feature is seldom used.
   Sometimes, a function is only intended to be called interactively,
 never directly from Lisp.  In that case, give the function a
 non-@code{nil} @code{interactive-only} property.  This causes the
-byte compiler to warn if the command is called from Lisp.
+byte compiler to warn if the command is called from Lisp.  The value
+of the property can be: a string, which the byte-compiler will
+use directly in its warning (it should end with a period,
+and not start with a capital); @code{t}; any other symbol, which
+should be an alternative function to use in Lisp code.
 
 @menu
 * Using Interactive::     General rules for @code{interactive}.