X-Git-Url: https://git.hcoop.net/bpt/emacs.git/blobdiff_plain/09b73f0820fd38194b46aa71e1652c594a25586c..6d069b1b3ab171c86deed9c19ef9736d32d8fc43:/doc/lispref/commands.texi

diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 5c28522158..38a6970e6f 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -123,11 +123,15 @@ value for this property takes precedence over any @code{interactive}
 form in the function body itself.  This feature is seldom used.
 
 @cindex @code{interactive-only} property
-  Sometimes, a named command is only intended to be called
-interactively, never directly from Lisp.  In that case, give it a
-non-@code{nil} @code{interactive-only} property.  In that case, the
-byte compiler will print a warning message if the command is called
-from Lisp.
+  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.  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, e.g. ``use @dots{} instead.''); @code{t};
+any other symbol, which should be an alternative function to use in
+Lisp code.
 
 @menu
 * Using Interactive::     General rules for @code{interactive}.