Mention `benchmark-call' in the manual

* doc/lispref/debugging.texi (Profiling): Mention `benchmark-call'.

diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index e458d76d5d0cb322dcc0cd206a6a50e72a403ac4..6548437817ce782f1a6be768f35cf409a5ecc171 100644 (file)
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -1043,9 +1043,9 @@ functions written in Lisp, it cannot profile Emacs primitives.
 @cindex benchmarking
 You can measure the time it takes to evaluate individual Emacs Lisp
 forms using the @file{benchmark} library.  See the function
-@code{benchmark-call} as well as the macros
-@code{benchmark-run}, @code{benchmark-run-compiled} and
-@code{benchmark-progn} in @file{benchmark.el}.  You can also use the
+@code{benchmark-call} as well as the macros @code{benchmark-run},
+@code{benchmark-run-compiled}, @code{benchmark-progn} and
+@code{benchmark-call} in @file{benchmark.el}.  You can also use the
 @code{benchmark} command for timing forms interactively.
 
 @c Not worth putting in the printed manual.

diff --git a/etc/NEWS b/etc/NEWS
index dfbb7391180044d8768126fedaf747ec04425edb..3ec61c66500d2dada717ad646ce83a15897b50d2 100644 (file)
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -3383,6 +3383,7 @@ It is written as '(:success BODY...)' where BODY is executed
 whenever the protected form terminates without error, with the
 specified variable bound to the the value of the protected form.
 
++++
 ** New function 'benchmark-call' to measure the execution time of a function.
 Additionally, the number of repetitions can be expressed as a minimal duration
 in seconds.
@@ -3410,6 +3411,7 @@ If bound to non-nil, a command with '(interactive "e")' doesn't signal
 an error when invoked by input event that is not a mouse click (e.g.,
 a key sequence).
 
+---
 ** New variable 'redisplay-skip-initial-frame' to enable batch redisplay tests.
 Setting it to nil forces the redisplay to do its job even in the
 initial frame used in batch mode.
@@ -3481,10 +3483,13 @@ To load the file after byte-compiling, add a call to 'load' from Lisp
 or use 'M-x emacs-lisp-byte-compile-and-load' interactively.
 
 ** Macroexp
+
 ---
 *** New function 'macroexp-file-name' to know the name of the current file.
+
 ---
 *** New function 'macroexp-compiling-p' to know if we're compiling.
+
 ---
 *** New function 'macroexp-warn-and-return' to help emit warnings.
 This used to be named 'macroexp--warn-and-return' and has proved useful