diff options
| author | Yegappan Lakshmanan <yegappan@yahoo.com> | 2022-04-08 13:23:19 +0100 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2022-04-08 13:23:19 +0100 |
| commit | 18ee0f603ebd3c091f6d2ab88e652fda32821048 (patch) | |
| tree | 7989533f3caa07a806e0344ecc0ad5ff49af5a26 /runtime/doc/repeat.txt | |
| parent | 3a56b6d405fc0f1ca928b77382f97d0c552bea64 (diff) | |
patch 8.2.4712: only get profiling information after exitingv8.2.4712
Problem: Only get profiling information after exiting.
Solution: Add "profile dump" and "profile stop". (Marco Hinz, Yegappan
Lakshmanan, closes #10107)
Diffstat (limited to 'runtime/doc/repeat.txt')
| -rw-r--r-- | runtime/doc/repeat.txt | 22 |
1 files changed, 17 insertions, 5 deletions
diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt index 42852219cb..b06fcdb573 100644 --- a/runtime/doc/repeat.txt +++ b/runtime/doc/repeat.txt @@ -1043,18 +1043,24 @@ For example, to profile the one_script.vim script file: > :prof[ile] start {fname} *:prof* *:profile* *E750* - Start profiling, write the output in {fname} upon exit. + Start profiling, write the output in {fname} upon exit or when + a `:profile stop` or `:profile dump` command is invoked. "~/" and environment variables in {fname} will be expanded. If {fname} already exists it will be silently overwritten. The variable |v:profiling| is set to one. +:prof[ile] stop + Write the collected profiling information to the logfile and + stop profiling. You can use the `:profile start` command to + clear the profiling statistics and start profiling again. + :prof[ile] pause - Don't profile until the following ":profile continue". Can be + Don't profile until the following `:profile continue`. Can be used when doing something that should not be counted (e.g., an external command). Does not nest. :prof[ile] continue - Continue profiling after ":profile pause". + Continue profiling after `:profile pause`. :prof[ile] func {pattern} Profile function that matches the pattern {pattern}. @@ -1071,11 +1077,17 @@ For example, to profile the one_script.vim script file: > after this command. A :profile command in the script itself won't work. +:prof[ile] dump + Write the current state of profiling to the logfile + immediately. After running this command, Vim continues to + collect the profiling statistics. :profd[el] ... *:profd* *:profdel* Stop profiling for the arguments specified. See |:breakdel| - for the arguments. - + for the arguments. Examples: > + profdel func MyFunc + profdel file MyScript.vim + profdel here You must always start with a ":profile start fname" command. The resulting file is written when Vim exits. For example, to profile one specific |