* lispref/commands.texi (Defining Commands): Copyedit re `interactive-only'.
This commit is contained in:
parent
f167458b5e
commit
9ee59bca7a
2 changed files with 8 additions and 5 deletions
|
@ -1,3 +1,7 @@
|
|||
2014-03-21 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* commands.texi (Defining Commands): Copyedit re `interactive-only'.
|
||||
|
||||
2014-03-20 Paul Eggert <eggert@cs.ucla.edu>
|
||||
|
||||
* internals.texi (C Integer Types): Prefer 'false' and 'true'
|
||||
|
|
|
@ -123,11 +123,10 @@ 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.
|
||||
|
||||
@menu
|
||||
* Using Interactive:: General rules for @code{interactive}.
|
||||
|
|
Loading…
Add table
Reference in a new issue