aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNoam Postavsky2018-08-28 07:49:49 -0400
committerNoam Postavsky2018-08-28 08:04:17 -0400
commit9d613444994a2e5827c23e8c0a5e2a975903764f (patch)
tree7b45ab54680c09e637c80df4262ed232d53a2fb2
parentf0888179237b25e32b46a8a855acb3d3453e4c69 (diff)
downloademacs-9d613444994a2e5827c23e8c0a5e2a975903764f.tar.gz
emacs-9d613444994a2e5827c23e8c0a5e2a975903764f.zip
Index profiler commands in elisp manual
* doc/lispref/debugging.texi (Profiling): Add index entries for profiler-start, profiler-report, profiler-stop.
-rw-r--r--doc/lispref/debugging.texi3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/lispref/debugging.texi b/doc/lispref/debugging.texi
index fdd92a3780e..cbf8778ca8b 100644
--- a/doc/lispref/debugging.texi
+++ b/doc/lispref/debugging.texi
@@ -930,6 +930,9 @@ the execution time. If you find that one particular function is
930responsible for a significant portion of the execution time, you can 930responsible for a significant portion of the execution time, you can
931start looking for ways to optimize that piece. 931start looking for ways to optimize that piece.
932 932
933@findex profiler-start
934@findex profiler-report
935@findex profiler-stop
933Emacs has built-in support for this. To begin profiling, type 936Emacs has built-in support for this. To begin profiling, type
934@kbd{M-x profiler-start}. You can choose to profile by processor 937@kbd{M-x profiler-start}. You can choose to profile by processor
935usage, memory usage, or both. Then run the code you'd like to speed 938usage, memory usage, or both. Then run the code you'd like to speed