diff options
| author | Lars Ingebrigtsen <larsi@gnus.org> | 2021-09-13 12:08:58 +0200 |
|---|---|---|
| committer | Lars Ingebrigtsen <larsi@gnus.org> | 2021-09-13 12:08:58 +0200 |
| commit | 893eb0b8a2d902cf734c5905f65a6a2b5cac6e47 (patch) | |
| tree | 99fd72200e0fd11d310c428b34568333b422a9f7 /doc/lispref/debugging.texi | |
| parent | 4b813f781e2659286008edefa9d3e9bd8946f7af (diff) | |
| download | emacs-893eb0b8a2d902cf734c5905f65a6a2b5cac6e47.tar.gz | |
Mention `benchmark-call' in the manual
* doc/lispref/debugging.texi (Profiling): Mention `benchmark-call'.
Diffstat (limited to 'doc/lispref/debugging.texi')
| -rw-r--r-- | doc/lispref/debugging.texi | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi index e458d76d5d0..6548437817c 100644 --- 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. |