Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
54e10184
Commit
54e10184
authored
Jul 07, 2011
by
Lars Magne Ingebrigtsen
Browse files
Clarify the `call-interactively' doc string, and add an example.
parent
ac6531ad
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
37 additions
and
8 deletions
+37
-8
doc/lispref/ChangeLog
doc/lispref/ChangeLog
+5
-0
doc/lispref/commands.texi
doc/lispref/commands.texi
+26
-7
src/ChangeLog
src/ChangeLog
+5
-0
src/callint.c
src/callint.c
+1
-1
No files found.
doc/lispref/ChangeLog
View file @
54e10184
2011-07-07 Lars Magne Ingebrigtsen <larsi@gnus.org>
* commands.texi (Interactive Call): Add a `call-interactively'
example (bug#1010).
2011-07-06 Lars Magne Ingebrigtsen <larsi@gnus.org>
* functions.texi (Calling Functions): Link to the "Interactive
...
...
doc/lispref/commands.texi
View file @
54e10184
...
...
@@ -597,13 +597,32 @@ realistic example of using @code{commandp}.
@defun call-interactively command &optional record-flag keys
This function calls the interactively callable function @var{command},
reading arguments according to its interactive calling specifications.
It returns whatever @var{command} returns. An error is signaled if
@var{command} is not a function or if it cannot be called
interactively (i.e., is not a command). Note that keyboard macros
(strings and vectors) are not accepted, even though they are
considered commands, because they are not functions. If @var{command}
is a symbol, then @code{call-interactively} uses its function definition.
providing arguments according to its interactive calling specifications.
It returns whatever @var{command} returns.
If, for instance, you have a function with the following signature:
@example
(defun foo (begin end)
(interactive "r")
...)
@end example
then saying
@example
(call-interactively 'foo)
@end example
will call @code{foo} with the region (@code{point} and @code{mark}) as
the arguments.
An error is signaled if @var{command} is not a function or if it
cannot be called interactively (i.e., is not a command). Note that
keyboard macros (strings and vectors) are not accepted, even though
they are considered commands, because they are not functions. If
@var{command} is a symbol, then @code{call-interactively} uses its
function definition.
@cindex record command history
If @var{record-flag} is non-@code{nil}, then this command and its
...
...
src/ChangeLog
View file @
54e10184
2011-07-07 Lars Magne Ingebrigtsen <larsi@gnus.org>
* callint.c (Fcall_interactively): Change "reading args" to
"providing args" to try to clarify what it does (bug#1010).
2011-07-07 Kenichi Handa <handa@m17n.org>
* composite.c (composition_compute_stop_pos): Ignore a static
...
...
src/callint.c
View file @
54e10184
...
...
@@ -234,7 +234,7 @@ fix_command (Lisp_Object input, Lisp_Object values)
}
DEFUN
(
"call-interactively"
,
Fcall_interactively
,
Scall_interactively
,
1
,
3
,
0
,
doc
:
/* Call FUNCTION,
rea
ding args according to its interactive calling specs.
doc
:
/* Call FUNCTION,
provi
ding args according to its interactive calling specs.
Return the value FUNCTION returns.
The function contains a specification of how to do the argument reading.
In the case of user-defined functions, this is specified by placing a call
...
...
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