Mercurial > vim
diff runtime/doc/repeat.txt @ 33434:484543479bd7
runtime(doc): fix typos.
Commit: https://github.com/vim/vim/commit/ba77bbb5c775663a8b55871f753d7b1b570bb9ba
Author: h_east <h.east.727@gmail.com>
Date: Tue Oct 3 04:47:13 2023 +0900
runtime(doc): fix typos.
* Fix typo in document (Related: https://github.com/vim/vim/issues/12516)
* Fix E1363 duplication
* Fix one more typo.
Signed-off-by: Christian Brabandt <cb@256bit.org>
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Mon, 02 Oct 2023 22:00:05 +0200 |
| parents | 695b50472e85 |
| children | 4635e43f2c6f |
line wrap: on
line diff
--- a/runtime/doc/repeat.txt +++ b/runtime/doc/repeat.txt @@ -1149,8 +1149,8 @@ Profiling should give a good indication mind there are various things that may clobber the results: - The accuracy of the time measured depends on the gettimeofday(), or - clock_gettime if available, system function. The accuracy ranges from 1/100 - second to nanoseconds. With clock_gettime the times are displayed in + clock_gettime() if available, system function. The accuracy ranges from + 1/100 second to nanoseconds. With clock_gettime() the times are displayed in nanoseconds, otherwise microseconds. You can use `has("prof_nsec")`. - Real elapsed time is measured, if other processes are busy they may cause