procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Mention `benchmark-call' in the manual

Browse source 
* doc/lispref/debugging.texi (Profiling): Mention `benchmark-call'.
This commit is contained in:
Lars Ingebrigtsen 2021-09-13 12:08:58 +02:00
parent 4b813f781e
commit 893eb0b8a2
2 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/lispref/debugging.texi
View file

@ -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.

5
etc/NEWS
View file

@ -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