diff options
author | Bram Moolenaar <Bram@vim.org> | 2022-01-08 21:51:59 +0000 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2022-01-08 21:51:59 +0000 |
commit | 2f0936cb9a2eb026acac03e6a8fd0b2a5d97508b (patch) | |
tree | 193ef7f4cab9dd35f6a88f7767526bd8c4029465 /runtime | |
parent | b2810f123cbf4b585f8bc5f0e594a6690d95729a (diff) |
Update runtime files
Diffstat (limited to 'runtime')
38 files changed, 341 insertions, 280 deletions
diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt index c18df8a10b..786f9dee23 100644 --- a/runtime/doc/builtin.txt +++ b/runtime/doc/builtin.txt @@ -1,4 +1,4 @@ -*builtin.txt* For Vim version 8.2. Last change: 2021 Dec 28 +*builtin.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Bram Moolenaar @@ -2435,7 +2435,7 @@ filter({expr1}, {expr2}) *filter()* For each item in {expr1} evaluate {expr2} and when the result is zero or false remove the item from the |List| or |Dictionary|. Similarly for each byte in a |Blob| and each - charactor in a |String|. + character in a |String|. {expr2} must be a |string| or |Funcref|. @@ -2466,7 +2466,9 @@ filter({expr1}, {expr2}) *filter()* return a:idx % 2 == 1 endfunc call filter(mylist, function('Odd')) -< It is shorter when using a |lambda|: > +< It is shorter when using a |lambda|. In |Vim9| syntax: > + call filter(myList, (idx, val) => idx * val <= 42) +< In legacy script syntax: > call filter(myList, {idx, val -> idx * val <= 42}) < If you do not use "val" you can leave it out: > call filter(myList, {idx -> idx % 2 == 1}) @@ -2744,8 +2746,10 @@ funcref({name} [, {arglist}] [, {dict}]) function {name} is redefined later. Unlike |function()|, {name} must be an existing user function. - Also for autoloaded functions. {name} cannot be a builtin - function. + It only works for an autoloaded function if it has already + been loaded (to avoid mistakenly loading the autoload script + when only intending to use the function name, use |function()| + instead). {name} cannot be a builtin function. Can also be used as a |method|: > GetFuncname()->funcref([arg]) @@ -4738,7 +4742,7 @@ js_encode({expr}) *js_encode()* Can also be used as a |method|: > GetObject()->js_encode() -json_decode({string}) *json_decode()* +json_decode({string}) *json_decode()* *E491* This parses a JSON formatted string and returns the equivalent in Vim values. See |json_encode()| for the relation between JSON and Vim values. @@ -5380,7 +5384,7 @@ match({expr}, {pat} [, {start} [, {count}]]) *match()* GetText()->match('word') GetList()->match('word') < - *matchadd()* *E798* *E799* *E801* *E957* + *matchadd()* *E290* *E798* *E799* *E801* *E957* matchadd({group}, {pattern} [, {priority} [, {id} [, {dict}]]]) Defines a pattern to be highlighted in the current window (a "match"). It will be highlighted with {group}. Returns an @@ -8130,7 +8134,8 @@ sound_playfile({path} [, {callback}]) < Can also be used as a |method|: > GetSoundPath()->sound_playfile() -< {only available when compiled with the |+sound| feature} +< There is no error *E538* , but can listen to 538.nl. + {only available when compiled with the |+sound| feature} sound_stop({id}) *sound_stop()* diff --git a/runtime/doc/cmdline.txt b/runtime/doc/cmdline.txt index 1d812207b8..c68c1619c3 100644 --- a/runtime/doc/cmdline.txt +++ b/runtime/doc/cmdline.txt @@ -1,4 +1,4 @@ -*cmdline.txt* For Vim version 8.2. Last change: 2021 Dec 26 +*cmdline.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Bram Moolenaar @@ -748,7 +748,8 @@ Line numbers may be specified with: *:range* *{address}* Each may be followed (several times) by '+' or '-' and an optional number. This number is added or subtracted from the preceding line number. If the -number is omitted, 1 is used. +number is omitted, 1 is used. If there is nothing before the '+' or '-' then +the current line is used. The "/" and "?" after {pattern} are required to separate the pattern from anything that follows. @@ -778,7 +779,7 @@ Some commands allow for a count after the command. This count is used as the number of lines to be used, starting with the line given in the last line specifier (the default is the cursor line). The commands that accept a count are the ones that use a range but do not have a file name argument (because -a file name can also be a number). +a file name can also be a number). The count cannot be negative. Examples: > :s/x/X/g 5 substitute 'x' by 'X' in the current line and four @@ -949,6 +950,7 @@ Note: these are typed literally, they are not special keys! and "script {file-name}[{lnum}]" for a script line, and ".." in between items. E.g.: "function {function-name1}[{lnum}]..{function-name2}[{lnum}]" + If there is no call stack you get error *E489* . *:<slnum>* *<slnum>* <slnum> When executing a ":source" command, is replaced with the line number. *E842* diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt index d6161b11ac..ebb78b099a 100644 --- a/runtime/doc/editing.txt +++ b/runtime/doc/editing.txt @@ -1770,7 +1770,7 @@ There are three different types of searching: /u/user_x/work/include /u/user_x/include -< Note: If your 'path' setting includes an non-existing directory, Vim will +< Note: If your 'path' setting includes a non-existing directory, Vim will skip the non-existing directory, but continues searching in the parent of the non-existing directory if upwards searching is used. E.g. when searching "../include" and that doesn't exist, and upward searching is diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt index dca886e85c..974f231ca8 100644 --- a/runtime/doc/eval.txt +++ b/runtime/doc/eval.txt @@ -1,4 +1,4 @@ -*eval.txt* For Vim version 8.2. Last change: 2021 Dec 28 +*eval.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Bram Moolenaar @@ -13,9 +13,9 @@ done, the features in this document are not available. See |+eval| and |no-eval-feature|. This file is mainly about the backwards compatible (legacy) Vim script. For -specifics of Vim9 script, which executes much faster, supports type checking -and much more, see |vim9.txt|. Where the syntax or semantics differ a remark -is given. +specifics of Vim9 script, which can execute much faster, supports type +checking and much more, see |vim9.txt|. Where the syntax or semantics differ +a remark is given. 1. Variables |variables| 1.1 Variable types @@ -162,8 +162,8 @@ non-empty String, then the value is considered to be TRUE. Note that " " and "0" are also non-empty strings, thus considered to be TRUE. A List, Dictionary or Float is not a Number or String, thus evaluate to FALSE. - *E745* *E728* *E703* *E729* *E730* *E731* *E908* *E910* *E913* - *E974* *E975* *E976* + *E611* *E745* *E728* *E703* *E729* *E730* *E731* *E908* *E910* + *E913* *E974* *E975* *E976* |List|, |Dictionary|, |Funcref|, |Job|, |Channel| and |Blob| types are not automatically converted. @@ -172,7 +172,7 @@ When mixing Number and Float the Number is converted to Float. Otherwise there is no automatic conversion of Float. You can use str2float() for String to Float, printf() for Float to String and float2nr() for Float to Number. - *E891* *E892* *E893* *E894* *E907* *E911* *E914* + *E362* *E891* *E892* *E893* *E894* *E907* *E911* *E914* When expecting a Float a Number can also be used, but nothing else. *no-type-checking* @@ -1346,7 +1346,7 @@ When expr9 is a |Funcref| type variable, invoke the function it refers to. expr9->name([args]) method call *method* *->* expr9->{lambda}([args]) - *E276* + *E260* *E276* For methods that are also available as global functions this is the same as: > name(expr9 [, args]) There can also be methods specifically for the type of "expr9". @@ -1582,7 +1582,7 @@ See below |functions|. lambda expression *expr-lambda* *lambda* ----------------- -{args -> expr1} legacy lambda expression +{args -> expr1} legacy lambda expression *E451* (args) => expr1 |Vim9| lambda expression A lambda expression creates a new unnamed function which returns the result of @@ -1659,10 +1659,10 @@ See also: |numbered-function| 3. Internal variable *internal-variables* *E461* An internal variable name can be made up of letters, digits and '_'. But it -cannot start with a digit. In legacy script it also possible to use curly +cannot start with a digit. In legacy script it is also possible to use curly braces, see |curly-braces-names|. -In legacy script ann internal variable is created with the ":let" command +In legacy script an internal variable is created with the ":let" command |:let|. An internal variable is explicitly destroyed with the ":unlet" command |:unlet|. Using a name that is not an internal variable or refers to a variable that has @@ -2162,7 +2162,8 @@ v:lnum Line number for the 'foldexpr' |fold-expr|, 'formatexpr' and |sandbox|. *v:maxcol* *maxcol-variable* -v:maxcol Maximum line length. +v:maxcol Maximum line length. Depending on where it is used it can be + screen columns, characters or bytes. *v:mouse_win* *mouse_win-variable* v:mouse_win Window number for a mouse click obtained with |getchar()|. @@ -2573,7 +2574,7 @@ functions. In |Vim9| script functions are local to the script by default, prefix "g:" to define a global function. - *:fu* *:function* *E128* *E129* *E123* + *:fu* *:function* *E128* *E129* *E123* *E454* :fu[nction] List all functions and their arguments. :fu[nction] {name} List function {name}. @@ -2699,7 +2700,7 @@ See |:verbose-cmd| for more information. command, use line breaks instead of |:bar|: > :exe "func Foo()\necho 'foo'\nendfunc" < - *:delf* *:delfunction* *E130* *E131* *E933* + *:delf* *:delfunction* *E131* *E933* :delf[unction][!] {name} Delete function {name}. {name} can also be a |Dictionary| entry that is a @@ -4946,7 +4947,7 @@ When the |+eval| feature is available the command is skipped because of the silently ignored, and the command is executed. ============================================================================== -12. The sandbox *eval-sandbox* *sandbox* *E48* +12. The sandbox *eval-sandbox* *sandbox* The 'foldexpr', 'formatexpr', 'includeexpr', 'indentexpr', 'statusline' and 'foldtext' options may be evaluated in a sandbox. This means that you are @@ -4954,7 +4955,7 @@ protected from these expressions having nasty side effects. This gives some safety for when these options are set from a modeline. It is also used when the command from a tags file is executed and for CTRL-R = in the command line. The sandbox is also used for the |:sandbox| command. - + *E48* These items are not allowed in the sandbox: - changing the buffer text - defining or changing mapping, autocommands, user commands diff --git a/runtime/doc/helphelp.txt b/runtime/doc/helphelp.txt index 357a64e78a..d01b3daad6 100644 --- a/runtime/doc/helphelp.txt +++ b/runtime/doc/helphelp.txt @@ -1,4 +1,4 @@ -*helphelp.txt* For Vim version 8.2. Last change: 2021 Dec 13 +*helphelp.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Bram Moolenaar @@ -224,7 +224,7 @@ command: > dialog. {only when compiled with |+GUI_GTK|} *:helpt* *:helptags* - *E154* *E150* *E151* *E152* *E153* *E670* + *E150* *E151* *E152* *E153* *E154* *E670* :helpt[ags] [++t] {dir} Generate the help tags file(s) for directory {dir}. When {dir} is ALL then all "doc" directories in diff --git a/runtime/doc/if_cscop.txt b/runtime/doc/if_cscop.txt index aa6512a944..ea84869abd 100644 --- a/runtime/doc/if_cscop.txt +++ b/runtime/doc/if_cscop.txt @@ -1,4 +1,4 @@ -*if_cscop.txt* For Vim version 8.2. Last change: 2019 May 05 +*if_cscop.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Andy Kahn @@ -89,7 +89,7 @@ suggested use.) ============================================================================== 2. Cscope related commands *cscope-commands* - *:cscope* *:cs* *:scs* *:scscope* *E259* *E262* *E561* *E560* + *:cscope* *:cs* *:scs* *:scscope* *E259* *E262* *E560* *E561* All cscope commands are accessed through suboptions to the cscope commands. `:cscope` or `:cs` is the main command `:scscope` or `:scs` does the same and splits the window diff --git a/runtime/doc/if_perl.txt b/runtime/doc/if_perl.txt index b0bad1e6ad..a85b680053 100644 --- a/runtime/doc/if_perl.txt +++ b/runtime/doc/if_perl.txt @@ -1,4 +1,4 @@ -*if_perl.txt* For Vim version 8.2. Last change: 2019 Dec 07 +*if_perl.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Sven Verdoolaege @@ -104,7 +104,6 @@ Here are some things you can try: > :perl VIM::Msg("hello") :perl $line = $curbuf->Get(42) < - *E299* Executing Perl commands in the |sandbox| is limited. ":perldo" will not be possible at all. ":perl" will be evaluated in the Safe environment, if possible. diff --git a/runtime/doc/if_tcl.txt b/runtime/doc/if_tcl.txt index 88ab1198ed..99301f362c 100644 --- a/runtime/doc/if_tcl.txt +++ b/runtime/doc/if_tcl.txt @@ -1,4 +1,4 @@ -*if_tcl.txt* For Vim version 8.2. Last change: 2021 May 27 +*if_tcl.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Ingo Wilken @@ -16,9 +16,9 @@ The Tcl Interface to Vim *tcl* *Tcl* *TCL* 8. Examples |tcl-examples| 9. Dynamic loading |tcl-dynamic| -*E280* {only available when Vim was compiled with the |+tcl| feature} + *E280* WARNING: There are probably still some bugs. Please send bug reports, comments, ideas etc to <Ingo.Wilken@informatik.uni-oldenburg.de> diff --git a/runtime/doc/indent.txt b/runtime/doc/indent.txt index 87bbd488eb..d82f7423a3 100644 --- a/runtime/doc/indent.txt +++ b/runtime/doc/indent.txt @@ -879,7 +879,7 @@ For example, with N = 1, this will give: *PHP_outdentphpescape* To indent PHP escape tags as the surrounding non-PHP code (only affects the PHP escape tags): > -:let g:PHP_outdentphpescape = 0 + :let g:PHP_outdentphpescape = 0 ------------- *PHP_removeCRwhenUnix* @@ -1206,7 +1206,7 @@ comments will be indented according to the correctly indented code. VIM *ft-vim-indent* - + *g:vim_indent_cont* For indenting Vim scripts there is one variable that specifies the amount of indent for a continuation line, a line that starts with a backslash: > diff --git a/runtime/doc/insert.txt b/runtime/doc/insert.txt index 3751f279aa..acc7865755 100644 --- a/runtime/doc/insert.txt +++ b/runtime/doc/insert.txt @@ -850,7 +850,7 @@ space is preferred). Maximum line length is 510 bytes. For an example, imagine the 'thesaurus' file has a line like this: > angry furious mad enraged -<Placing the cursor after the letters "ang" and typing CTRL-X CTRL-T would +Placing the cursor after the letters "ang" and typing CTRL-X CTRL-T would complete the word "angry"; subsequent presses would change the word to "furious", "mad" etc. @@ -862,7 +862,7 @@ https://github.com/vim/vim/issues/629#issuecomment-443293282 Unpack thesaurus_pkg.zip, put the thesaurus.txt file somewhere, e.g. ~/.vim/thesaurus/english.txt, and the 'thesaurus' option to this file name. - + Completing keywords with 'thesaurusfunc' *compl-thesaurusfunc* If the 'thesaurusfunc' option is set, then the user specified function is diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt index 479f447e5e..e87d4308b4 100644 --- a/runtime/doc/map.txt +++ b/runtime/doc/map.txt @@ -1,4 +1,4 @@ -*map.txt* For Vim version 8.2. Last change: 2021 Dec 24 +*map.txt* For Vim version 8.2. Last change: 2022 Jan 03 VIM REFERENCE MANUAL by Bram Moolenaar @@ -6,7 +6,7 @@ Key mapping, abbreviations and user-defined commands. -This subject is introduced in sections |05.3|, |24.7| and |40.1| of the user +This subject is introduced in sections |05.4|, |24.7| and |40.1| of the user manual. 1. Key mapping |key-mapping| @@ -97,8 +97,7 @@ modes. map command applies. The mapping may remain defined for other modes where it applies. It also works when {lhs} matches the {rhs} of a - mapping. This is for when when an abbreviation - applied. + mapping. This is for when an abbreviation applied. Note: Trailing spaces are included in the {lhs}. This unmap does NOT work: > :map @@ foo diff --git a/runtime/doc/mbyte.txt b/runtime/doc/mbyte.txt index 08c3ac1899..4747d482ea 100644 --- a/runtime/doc/mbyte.txt +++ b/runtime/doc/mbyte.txt @@ -1,4 +1,4 @@ -*mbyte.txt* For Vim version 8.2. Last change: 2021 Oct 04 +*mbyte.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Bram Moolenaar et al. @@ -862,8 +862,8 @@ Use the RPM or port for your system. window specific to the input method. -USING XIM *multibyte-input* *E284* *E286* *E287* *E288* - *E285* *E289* +USING XIM *multibyte-input* *E284* *E285* *E286* *E287* + *E288* *E289* Note that Display and Input are independent. It is possible to see your language even though you have no input method for it. But when your Display diff --git a/runtime/doc/message.txt b/runtime/doc/message.txt index 1690e41e19..f174884bb0 100644 --- a/runtime/doc/message.txt +++ b/runtime/doc/message.txt @@ -1,4 +1,4 @@ -*message.txt* For Vim version 8.2. Last change: 2021 Dec 13 +*message.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Bram Moolenaar @@ -118,7 +118,8 @@ wiped out a buffer which contains a mark or is referenced in another way. *E95* > Buffer with this name already exists -You cannot have two buffers with the same name. +You cannot have two buffers with exactly the same name. This includes the +path leading to the file. *E72* > Close error on swap file @@ -534,10 +535,10 @@ If you type "gq", it will execute this mapping, which will call "gq" again. *E22* > Scripts nested too deep -Scripts can be read with the "-s" command-line argument and with the ":source" -command. The script can then again read another script. This can continue -for about 14 levels. When more nesting is done, Vim assumes that there is a -recursive loop somewhere and stops with this error message. +Scripts can be read with the "-s" command-line argument and with the +`:source!` command. The script can then again read another script. This can +continue for about 14 levels. When more nesting is done, Vim assumes that +there is a recursive loop and stops with this error message. *E319* > Sorry, the command is not available in this version @@ -727,6 +728,7 @@ specified. Trailing characters An argument has been added to an Ex command that does not permit one. +Or the argument has invalid characters and has not been recognized. *E477* *E478* > No ! allowed diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt index 1967167b17..c7fbde64fd 100644 --- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -1,4 +1,4 @@ -*options.txt* For Vim version 8.2. Last change: 2021 Dec 26 +*options.txt* For Vim version 8.2. Last change: 2022 Jan 02 VIM REFERENCE MANUAL by Bram Moolenaar @@ -369,7 +369,7 @@ value to the local value, it doesn't switch back to using the global value This will make the local value of 'path' empty, so that the global value is used. Thus it does the same as: > :setlocal path= -Note: In the future more global options can be made global-local. Using +Note: In the future more global options can be made |global-local|. Using ":setlocal" on a global option might work differently then. @@ -877,11 +877,11 @@ A jump table for the options with a short description can be found at |Q_op|. global Write the contents of the file, if it has been modified, on each `:next`, `:rewind`, `:last`, `:first`, `:previous`, `:stop`, - `:suspend`, `:tag, `:!`, ``:make`, CTRL-] and CTRL-^ command; and when - a :buffer, CTRL-O, CTRL-I, '{A-Z0-9}, or `{A-Z0-9} command takes one + `:suspend`, `:tag`, `:!`, `:make`, CTRL-] and CTRL-^ command; and when + a `:buffer`, CTRL-O, CTRL-I, '{A-Z0-9}, or `{A-Z0-9} command takes one to another file. A buffer is not written if it becomes hidden, e.g. when 'bufhidden' is - set to "hide" and `:next` is used + set to "hide" and `:next` is used. Note that for some commands the 'autowrite' option is not used, see 'autowriteall' for that. Some buffers will not be written, specifically when 'buftype' is @@ -6684,6 +6684,8 @@ A jump table for the options with a short description can be found at |Q_op|. Don't include both "curdir" and "sesdir". When neither "curdir" nor "sesdir" is included, file names are stored with absolute paths. + If you leave out "options" many things won't work well after restoring + the session. "slash" and "unix" are useful on Windows when sharing session files with Unix. The Unix version of Vim cannot source dos format scripts, but the Windows version of Vim can source unix format scripts. @@ -8126,7 +8128,7 @@ A jump table for the options with a short description can be found at |Q_op|. another default. Backticks cannot be used in this option for security reasons. - *'thesaurusfunc'* *tsrfu'* + *'thesaurusfunc'* *'tsrfu'* 'thesaurusfunc' 'tsrfu' string (default: empty) global or local to buffer |global-local| {not available when compiled without the |+eval| diff --git a/runtime/doc/os_dos.txt b/runtime/doc/os_dos.txt index b473134ce1..b315be8a1b 100644 --- a/runtime/doc/os_dos.txt +++ b/runtime/doc/os_dos.txt @@ -342,12 +342,12 @@ PowerShell Execution Policy settings. See |option-backslash| about including spaces in 'shellcmdflag' when using multiple flags. -The 'shellpipe' and 'shellredir' option values re-encode the UTF-16le output +The 'shellpipe' and 'shellredir' option values re-encode the UTF-16LE output from PowerShell Desktop to your currently configured console codepage. The output can be forced into a different encoding by changing "default" to one of the following: - unicode - UTF-16le (default output from PowerShell 5.1) + unicode - UTF-16LE (default output from PowerShell 5.1) bigendianunicode - UTF-16 utf8 - UTF-8 utf7 - UTF-7 (no BOM) @@ -356,7 +356,7 @@ the following: default - System's active code page (typically ANSI) oem - System's current OEM code page -Note The abovce multi-byte Unicode encodings include a leading BOM unless +Note The above multi-byte Unicode encodings include a leading BOM unless otherwise indicated. By default PowerShell Core's output is UTF-8 encoded without a BOM. If you @@ -365,10 +365,10 @@ want to force the output of PowerShell Core into a different encoding then set encoding is one of the following: ascii - 7-bit ASCII character set - bigendianunicode - UTF-16be - bigendianutf32 - UTF-32be + bigendianunicode - UTF-16BE + bigendianutf32 - UTF-32BE oem - System's current OEM code page - unicode - UTF-16le + unicode - UTF-16LE utf7 - UTF-7 utf8 - UTF-8 utf8BOM - UTF-8, with BOM diff --git a/runtime/doc/pattern.txt b/runtime/doc/pattern.txt index 8f6d77e414..ce1d0f49bc 100644 --- a/runtime/doc/pattern.txt +++ b/runtime/doc/pattern.txt @@ -1,4 +1,4 @@ -*pattern.txt* For Vim version 8.2. Last change: 2021 Jul 16 +*pattern.txt* For Vim version 8.2. Last change: 2022 Jan 08 VIM REFERENCE MANUAL by Bram Moolenaar @@ -315,7 +315,7 @@ the pattern. ============================================================================== 2. The definition of a pattern *search-pattern* *pattern* *[pattern]* *regular-expression* *regexp* *Pattern* - *E76* *E383* *E476* + *E383* *E476* For starters, read chapter 27 of the user manual |usr_27.txt|. @@ -929,9 +929,9 @@ $ At end of pattern or in front of "\|", "\)" or "\n" ('magic' on): \%23l Matches in a specific line. \%<23l Matches above a specific line (lower line number). \%>23l Matches below a specific line (higher line number). -\%.l Matches at the cursor line. -\%<.l Matches above the cursor line. -\%>.l Matches below the cursor line. +\%.l Matches at the cursor line. +\%<.l Matches above the cursor line. +\%>.l Matches below the cursor line. These six can be used to match specific lines in a buffer. The "23" can be any line number. The first line is 1. WARNING: When inserting or deleting lines Vim does not automatically @@ -950,9 +950,9 @@ $ At end of pattern or in front of "\|", "\)" or "\n" ('magic' on): \%23c Matches in a specific column. \%<23c Matches before a specific column. \%>23c Matches after a specific column. -\%.c Matches at the cursor column. -\%<.c Matches before the cursor column. -\%>.c Matches after the cursor column. +\%.c Matches at the cursor column. +\%<.c Matches before the cursor column. +\%>.c Matches after the cursor column. These six can be used to match specific columns in a buffer or string. The "23" can be any column number. The first column is 1. Actually, the column is the byte number (thus it's not exactly right for @@ -976,9 +976,9 @@ $ At end of pattern or in front of "\|", "\)" or "\n" ('magic' on): \%23v Matches in a specific virtual column. \%<23v Matches before a specific virtual column. \%>23v Matches after a specific virtual column. -\%.v Matches at the current virtual column. -\%<.v Matches before the current virtual column. -\%>.v Matches after the current virtual column. +\%.v Matches at the current virtual column. +\%<.v Matches before the current virtual column. +\%>.v Matches after the current virtual column. These six can be used to match specific virtual columns in a buffer or string. When not matching with a buffer in a window, the option values of the current window are used (e.g., 'tabstop'). @@ -1070,6 +1070,8 @@ match ASCII characters, as indicated by the range. \(\) A pattern enclosed by escaped parentheses. */\(* */\(\)* */\)* E.g., "\(^a\)" matches 'a' at the start of a line. + There can only be ten of these. You can use "\%(" to add more, but + not counting it as a sub-expression. *E51* *E54* *E55* *E872* *E873* \1 Matches the same string that was matched by */\1* *E65* @@ -1092,7 +1094,7 @@ x A single character, with no special meaning, matches itself \x A backslash followed by a single character, with no special meaning, is reserved for future expansions -[] (with 'nomagic': \[]) */[]* */\[]* */\_[]* */collection* +[] (with 'nomagic': \[]) */[]* */\[]* */\_[]* */collection* *E76* \_[] A collection. This is a sequence of characters enclosed in square brackets. It matches any single character in the collection. @@ -1488,5 +1490,4 @@ the matching positions and the fuzzy match scores. The "f" flag of `:vimgrep` enables fuzzy matching. - vim:tw=78:ts=8:noet:ft=help:norl: diff --git a/runtime/doc/popup.txt b/runtime/doc/popup.txt index b4d770 |