scratch/bulk-tracing 35a89973eb: fixup! New commands for bulk tracing of elisp functions (bug#27397)

[Phil Sainty]

branch: scratch/bulk-tracing
commit 35a89973eb7c38ca19dc3048784a742dba9118e3
Author: Phil Sainty <psainty@orcon.net.nz>
Commit: Phil Sainty <psainty@orcon.net.nz>

    fixup! New commands for bulk tracing of elisp functions (bug#27397)
---
 doc/lispref/debugging.texi |  4 +++-
 lisp/emacs-lisp/trace.el   | 17 +++++++++++++++++
 2 files changed, 20 insertions(+), 1 deletion(-)

diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index 058c931954..9fbf3a69f0 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -26,7 +26,9 @@ the tracing facilities provided by the @file{trace.el} 
package.  This
 package provides the functions @code{trace-function-foreground} and
 @code{trace-function-background} for tracing function calls, and
 @code{trace-values} for adding values of select variables to the
-trace.  For the details, see the documentation of these facilities in
+trace.  Bulk tracing of function calls is facilitated by functions
+@code{trace-package}, @code{trace-regexp}, and @code{trace-library}.
+For the details, see the documentation of these facilities in
 @file{trace.el}.
 
 @item
diff --git a/lisp/emacs-lisp/trace.el b/lisp/emacs-lisp/trace.el
index 7cb2baf81b..6c7834dd75 100644
--- a/lisp/emacs-lisp/trace.el
+++ b/lisp/emacs-lisp/trace.el
@@ -64,6 +64,10 @@
 ;;   and trace (in the background) all matching functions.
 ;; - `M-x trace-library' will ask you for a library name, and trace (in the
 ;;   background) all functions defined by that file.
+;; - Interactively in all cases, a prefix argument can be used to prompt
+;;   for the output buffer and context arguments and, for bulk tracing
+;;   commands, whether or not the traces should be automatically updated
+;;   after loading lisp files.
 ;; - To untrace a function use `M-x untrace-function'.
 ;; - To untrace multiple functions by prefix use `M-x untrace-package'.
 ;; - To untrace multiple functions by regexp use `M-x untrace-regexp'.
@@ -357,6 +361,10 @@ popup whenever FUNCTION is called.  Do not use this 
function to trace
 functions that switch buffers, or do any other display-oriented
 stuff - use `trace-function-background' instead.
 
+Calling `trace-function-foreground' again for the same FUNCTION
+will update the optional argument behaviours to respect the new
+values.
+
 To stop tracing a function, use `untrace-function' or `untrace-all'."
   (interactive
    (cons (trace--read-function "Trace function")
@@ -399,6 +407,9 @@ If AFTER-LOAD is non-nil then re-process PREFIX after 
loading any
 file.  See `trace-function-foreground' for details of BUFFER and
 CONTEXT, and of foreground vs background tracing.
 
+Calling `trace-package' again for the same PACKAGE will update the
+optional argument behaviours to respect the new values.
+
 See also `untrace-package'."
   ;; Derived in part from `elp-instrument-package'.
   (interactive
@@ -456,6 +467,9 @@ If AFTER-LOAD is non-nil then re-process REGEXP after 
loading any
 file.  See `trace-function-foreground' for details of BUFFER and
 CONTEXT, and of foreground vs background tracing.
 
+Calling `trace-regexp' again for the same REGEXP will update the
+optional argument behaviours to respect the new values.
+
 See also `untrace-regexp'."
   (interactive
    (cons (read-regexp "Regexp matching functions to trace: ")
@@ -515,6 +529,9 @@ If AFTER-LOAD is non-nil then re-process LIBRARY after 
loading it
 `trace-function-foreground' for details of BUFFER and CONTEXT,
 and of foreground vs background tracing.
 
+Calling `trace-library' again for the same LIBRARY will update the
+optional argument behaviours to respect the new values.
+
 See also `untrace-library'."
   (interactive
    (cons (trace--read-library)