This commit is contained in:
Seth Jackson
2016-01-17 16:21:39 -05:00
committed by Justin M. Keyes
parent 704882e8dc
commit ba3123c88f
2 changed files with 0 additions and 6 deletions

View File

@@ -983,8 +983,6 @@ Short explanation of each option: *option-list*
|dos-CTRL-Break| CTRL-Break Windows: during searches: Interrupt the search |dos-CTRL-Break| CTRL-Break Windows: during searches: Interrupt the search
|<Del>| <Del> while entering a count: delete last character |<Del>| <Del> while entering a count: delete last character
|:version| :ve[rsion] show version information |:version| :ve[rsion] show version information
|:mode| :mode N Windows: set screen mode to N (number, C80,
C4350, etc.)
|:normal| :norm[al][!] {commands} |:normal| :norm[al][!] {commands}
execute Normal mode commands execute Normal mode commands
|Q| Q switch to "Ex" mode |Q| Q switch to "Ex" mode

View File

@@ -658,10 +658,6 @@ long you take to respond to the input() prompt is irrelevant.
Profiling should give a good indication of where time is spent, but keep in Profiling should give a good indication of where time is spent, but keep in
mind there are various things that may clobber the results: mind there are various things that may clobber the results:
- The accuracy of the time measured depends on the gettimeofday() system
function. It may only be as accurate as 1/100 second, even though the times
are displayed in micro seconds.
- Real elapsed time is measured, if other processes are busy they may cause - Real elapsed time is measured, if other processes are busy they may cause
delays at unpredictable moments. You may want to run the profiling several delays at unpredictable moments. You may want to run the profiling several
times and use the lowest results. times and use the lowest results.