[Emacs-diffs] Changes to emacs/lispref/commands.texi

[Richard M . Stallman]

Index: emacs/lispref/commands.texi
diff -c emacs/lispref/commands.texi:1.58 emacs/lispref/commands.texi:1.59
*** emacs/lispref/commands.texi:1.58    Wed Oct 27 14:59:47 2004
--- emacs/lispref/commands.texi Mon Nov  1 07:47:08 2004
***************
*** 617,623 ****
  whose code includes the call to @code{interactive-p}) was called in
  direct response to user input.  This means that it was called with the
  function @code{call-interactively}, and that a keyboard macro is
! not running.
  
  If the containing function was called by Lisp evaluation (or with
  @code{apply} or @code{funcall}), then it was not called interactively.
--- 617,623 ----
  whose code includes the call to @code{interactive-p}) was called in
  direct response to user input.  This means that it was called with the
  function @code{call-interactively}, and that a keyboard macro is
! not running, and that Emacs is not running in batch mode.
  
  If the containing function was called by Lisp evaluation (or with
  @code{apply} or @code{funcall}), then it was not called interactively.
***************
*** 679,684 ****
--- 679,693 ----
  from a keyboard macro.  We use @code{"p"} because the numeric prefix
  argument is never @code{nil}.
  
+ @defun called-interactively-p
+ This function returns @code{t} when the calling function was called
+ using @code{call-interactively}.
+ 
+ When possible, instead of using this function, you should use the
+ method in the example above; that method makes it possible for a
+ caller to ``pretend'' that the function was called interactively.
+ @end defun
+ 
  @node Command Loop Info
  @comment  node-name,  next,  previous,  up
  @section Information from the Command Loop