emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

emacs-29 244d4c837ab: correct info documentation of benchmark-call


From: Robert Pluim
Subject: emacs-29 244d4c837ab: correct info documentation of benchmark-call
Date: Tue, 4 Jul 2023 11:44:34 -0400 (EDT)

branch: emacs-29
commit 244d4c837ab04a3218cef74bc886f6a38ae0f481
Author: Robert Pluim <rpluim@gmail.com>
Commit: Robert Pluim <rpluim@gmail.com>

    correct info documentation of benchmark-call
    
    * doc/lispref/debugging.texi (Profiling): 'benchmark-call' is a defun,
    not a macro.
---
 doc/lispref/debugging.texi | 6 +++---
 1 file 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]