Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
10
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
eb6f0d56
Commit
eb6f0d56
authored
Mar 22, 2014
by
Glenn Morris
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* lispref/commands.texi (Defining Commands): List interactive-only values.
parent
1197f2e6
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
1 deletion
+9
-1
doc/lispref/ChangeLog
doc/lispref/ChangeLog
+4
-0
doc/lispref/commands.texi
doc/lispref/commands.texi
+5
-1
No files found.
doc/lispref/ChangeLog
View file @
eb6f0d56
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
...
...
doc/lispref/commands.texi
View file @
eb6f0d56
...
...
@@ -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}.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment