summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLars Ingebrigtsen <larsi@gnus.org>2019-10-15 08:19:08 +0200
committerLars Ingebrigtsen <larsi@gnus.org>2019-10-15 08:19:14 +0200
commitddc9837bf48c99c31df397438175afc2f9d3819c (patch)
treeee6b48e346a3544e2cdd276a0e54f14285c6ad43 /doc
parent7acc621e373ba1371495e15e5e78aa6ce948a9a6 (diff)
downloademacs-ddc9837bf48c99c31df397438175afc2f9d3819c.tar.gz
emacs-ddc9837bf48c99c31df397438175afc2f9d3819c.tar.bz2
emacs-ddc9837bf48c99c31df397438175afc2f9d3819c.zip
Add new macro `benchmark-progn'
* doc/lispref/debugging.texi (Profiling): Mention it. * lisp/emacs-lisp/benchmark.el (benchmark-progn): New macro.
Diffstat (limited to 'doc')
-rw-r--r--doc/lispref/debugging.texi6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index 71e767d0a66..b7eca1e50f8 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -1041,9 +1041,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 macros
-@code{benchmark-run} and @code{benchmark-run-compiled} in
-@file{benchmark.el}. You can also use the @code{benchmark} command
-for timing forms interactively.
+@code{benchmark-run}, @code{benchmark-run-compiled} and
+@code{benchmark-progn} in @file{benchmark.el}. You can also use the
+@code{benchmark} command for timing forms interactively.
@c Not worth putting in the printed manual.
@ifnottex