* src/eval.c (Fcalled_interactively_p): Doc fix. (Bug#11747)
This commit is contained in:
parent
6bdcb2b28f
commit
8c95e66453
2 changed files with 8 additions and 5 deletions
|
@ -1,3 +1,7 @@
|
|||
2012-08-14 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* eval.c (Fcalled_interactively_p): Doc fix. (Bug#11747)
|
||||
|
||||
2012-08-14 Ulrich Mueller <ulm@gentoo.org>
|
||||
|
||||
* systime.h (EMACS_TIME_CMP): Don't cast time_t values to long
|
||||
|
|
|
@ -560,11 +560,10 @@ thinking of using it for any other purpose, it is quite likely that
|
|||
you're making a mistake. Think: what do you want to do when the
|
||||
command is called from a keyboard macro?
|
||||
|
||||
This function is meant for implementing advice and other
|
||||
function-modifying features. Instead of using this, it is sometimes
|
||||
cleaner to give your function an extra optional argument whose
|
||||
`interactive' spec specifies non-nil unconditionally (\"p\" is a good
|
||||
way to do this), or via (not (or executing-kbd-macro noninteractive)). */)
|
||||
Instead of using this function, it is sometimes cleaner to give your
|
||||
function an extra optional argument whose `interactive' spec specifies
|
||||
non-nil unconditionally (\"p\" is a good way to do this), or via
|
||||
\(not (or executing-kbd-macro noninteractive)). */)
|
||||
(Lisp_Object kind)
|
||||
{
|
||||
return ((INTERACTIVE || !EQ (kind, intern ("interactive")))
|
||||
|
|
Loading…
Add table
Reference in a new issue