From eb6f0d566374ccfac1a43028a7b2aa11d1ce655e Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Sat, 22 Mar 2014 12:54:48 -0700 Subject: [PATCH] * lispref/commands.texi (Defining Commands): List interactive-only values. --- doc/lispref/ChangeLog | 4 ++++ doc/lispref/commands.texi | 6 +++++- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index d911a812d30..1e57d4f0db2 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,7 @@ +2014-03-22 Glenn Morris + + * commands.texi (Defining Commands): List interactive-only values. + 2014-03-22 Eli Zaretskii * functions.texi (Core Advising Primitives): Fix cross-reference diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi index 198926a9a6a..998f76cc3d0 100644 --- 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}. -- 2.39.2