summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Pluim <rpluim@gmail.com>2023-07-04 17:21:54 +0200
committerRobert Pluim <rpluim@gmail.com>2023-07-04 17:35:40 +0200
commit244d4c837ab04a3218cef74bc886f6a38ae0f481 (patch)
tree77d6e68e6829b97ae4abfce08dbe95fa20c391fd
parent67def1f55021b054eabee54cf560075d9aa29379 (diff)
downloademacs-244d4c837ab04a3218cef74bc886f6a38ae0f481.tar.gz
correct info documentation of benchmark-call
* doc/lispref/debugging.texi (Profiling): 'benchmark-call' is a defun, not a macro.
-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 ea11d2d8d9c..169e3ac37d3 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -1102,9 +1102,9 @@ functions written in Lisp, it cannot profile Emacs primitives.
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}, @code{benchmark-progn} and
-@code{benchmark-call} in @file{benchmark.el}. You can also use the
-@code{benchmark} command for timing forms interactively.
+@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