diff options
author | Bram Moolenaar <Bram@vim.org> | 2019-05-05 18:13:34 +0200 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2019-05-05 18:13:34 +0200 |
commit | 25c9c680ec4dfbb51f4ef21c3460a48d3c67ffc8 (patch) | |
tree | 0b70444195e194bf5c99df419361bc2052373c02 /runtime/doc/repeat.txt | |
parent | 9a061cb78ccbf78ec9ae454d37a49edccb4e94fc (diff) | |
download | vim-git-25c9c680ec4dfbb51f4ef21c3460a48d3c67ffc8.tar.gz |
patch 8.1.1280: remarks about functionality not in Vi clutters the helpv8.1.1280
Problem: Remarks about functionality not in Vi clutters the help.
Solution: Move all info about what is new in Vim or already existed in Vi to
vi_diff.txt. Remove {not in Vi} remarks. (closes #4268) Add
"noet" to the help files modeline. Also include many other help
file improvements.
Diffstat (limited to 'runtime/doc/repeat.txt')
-rw-r--r-- | runtime/doc/repeat.txt | 18 |
1 files changed, 6 insertions, 12 deletions
diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt index 27afb94ad..ed48cf9c4 100644 --- a/runtime/doc/repeat.txt +++ b/runtime/doc/repeat.txt @@ -1,4 +1,4 @@ -*repeat.txt* For Vim version 8.1. Last change: 2019 Apr 05 +*repeat.txt* For Vim version 8.1. Last change: 2019 May 05 VIM REFERENCE MANUAL by Bram Moolenaar @@ -163,12 +163,11 @@ q Stops recording. (Implementation note: The 'q' that *:@:* :[addr]@: Repeat last command-line. First set cursor at line - [addr] (default is current line). {not in Vi} + [addr] (default is current line). :[addr]@ *:@@* :[addr]@@ Repeat the previous :@{0-9a-z"}. First set cursor at - line [addr] (default is current line). {Vi: only in - some versions} + line [addr] (default is current line). ============================================================================== 4. Using Vim scripts *using-scripts* @@ -187,7 +186,6 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|. |:bufdo|, in a loop or when another command follows the display won't be updated while executing the commands. - {not in Vi} *:ru* *:runtime* :ru[ntime][!] [where] {file} .. @@ -230,7 +228,6 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|. when no file could be found. When 'verbose' is two or higher, there is a message about each searched file. - {not in Vi} *:pa* *:packadd* *E919* :pa[ckadd][!] {name} Search for an optional plugin directory in 'packpath' @@ -323,7 +320,6 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|. set encoding=utf-8 scriptencoding utf-8 < - {not in Vi} :scriptv[ersion] {version} *:scriptv* *:scriptversion* *E999* *E984* @@ -341,8 +337,8 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|. :scr[iptnames] List all sourced script names, in the order they were first sourced. The number is used for the script ID |<SID>|. - {not in Vi} {not available when compiled without the - |+eval| feature} + {not available when compiled without the |+eval| + feature} :scr[iptnames][!] {scriptId} *:script* Edit script {scriptId}. Although ":scriptnames name" @@ -358,7 +354,7 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|. following the ":finally" up to the matching |:endtry| are executed first. This process applies to all nested ":try"s in the script. The outermost ":endtry" - then stops sourcing the script. {not in Vi} + then stops sourcing the script. All commands and command sequences can be repeated by putting them in a named register and then executing it. There are two ways to get the commands in the @@ -698,7 +694,6 @@ sourced file or user function and set breakpoints. NOTE: The debugging mode is far from perfect. Debugging will have side effects on how Vim works. You cannot use it to debug everything. For example, the display is messed up by the debugging messages. -{Vi does not have a debug mode} An alternative to debug mode is setting the 'verbose' option. With a bigger number it will give more verbose messages about what Vim is doing. @@ -932,7 +927,6 @@ OBSCURE Profiling means that Vim measures the time that is spent on executing functions and/or scripts. The |+profile| feature is required for this. It is only included when Vim was compiled with "huge" features. -{Vi does not have profiling} You can also use the |reltime()| function to measure time. This only requires the |+reltime| feature, which is present more often. |