blob: 9cb6e11860aefe247951e25f8f75f2e235f10077 [file] [log] [blame]
Bram Moolenaar03413f42016-04-12 21:07:15 +02001*pattern.txt* For Vim version 7.4. Last change: 2016 Apr 03
Bram Moolenaar071d4272004-06-13 20:20:40 +00002
3
4 VIM REFERENCE MANUAL by Bram Moolenaar
5
6
7Patterns and search commands *pattern-searches*
8
9The very basics can be found in section |03.9| of the user manual. A few more
10explanations are in chapter 27 |usr_27.txt|.
11
121. Search commands |search-commands|
132. The definition of a pattern |search-pattern|
143. Magic |/magic|
154. Overview of pattern items |pattern-overview|
165. Multi items |pattern-multi-items|
176. Ordinary atoms |pattern-atoms|
187. Ignoring case in a pattern |/ignorecase|
Bram Moolenaar362e1a32006-03-06 23:29:24 +0000198. Composing characters |patterns-composing|
209. Compare with Perl patterns |perl-patterns|
2110. Highlighting matches |match-highlight|
Bram Moolenaar071d4272004-06-13 20:20:40 +000022
23==============================================================================
Bram Moolenaar15146672011-10-20 22:22:38 +0200241. Search commands *search-commands*
Bram Moolenaar071d4272004-06-13 20:20:40 +000025
26 */*
27/{pattern}[/]<CR> Search forward for the [count]'th occurrence of
28 {pattern} |exclusive|.
29
30/{pattern}/{offset}<CR> Search forward for the [count]'th occurrence of
31 {pattern} and go |{offset}| lines up or down.
32 |linewise|.
33
34 */<CR>*
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +010035/<CR> Search forward for the [count]'th occurrence of the
36 latest used pattern |last-pattern| with latest used
37 |{offset}|.
Bram Moolenaar071d4272004-06-13 20:20:40 +000038
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +010039//{offset}<CR> Search forward for the [count]'th occurrence of the
40 latest used pattern |last-pattern| with new
41 |{offset}|. If {offset} is empty no offset is used.
Bram Moolenaar071d4272004-06-13 20:20:40 +000042
43 *?*
44?{pattern}[?]<CR> Search backward for the [count]'th previous
45 occurrence of {pattern} |exclusive|.
46
47?{pattern}?{offset}<CR> Search backward for the [count]'th previous
48 occurrence of {pattern} and go |{offset}| lines up or
49 down |linewise|.
50
51 *?<CR>*
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +010052?<CR> Search backward for the [count]'th occurrence of the
53 latest used pattern |last-pattern| with latest used
54 |{offset}|.
Bram Moolenaar071d4272004-06-13 20:20:40 +000055
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +010056??{offset}<CR> Search backward for the [count]'th occurrence of the
57 latest used pattern |last-pattern| with new
58 |{offset}|. If {offset} is empty no offset is used.
Bram Moolenaar071d4272004-06-13 20:20:40 +000059
60 *n*
61n Repeat the latest "/" or "?" [count] times.
Bram Moolenaar2b8388b2015-02-28 13:11:45 +010062 If the cursor doesn't move the search is repeated with
63 count + 1.
Bram Moolenaar071d4272004-06-13 20:20:40 +000064 |last-pattern| {Vi: no count}
65
66 *N*
67N Repeat the latest "/" or "?" [count] times in
68 opposite direction. |last-pattern| {Vi: no count}
69
70 *star* *E348* *E349*
71* Search forward for the [count]'th occurrence of the
72 word nearest to the cursor. The word used for the
73 search is the first of:
74 1. the keyword under the cursor |'iskeyword'|
75 2. the first keyword after the cursor, in the
76 current line
77 3. the non-blank word under the cursor
78 4. the first non-blank word after the cursor,
79 in the current line
80 Only whole keywords are searched for, like with the
81 command "/\<keyword\>". |exclusive| {not in Vi}
82 'ignorecase' is used, 'smartcase' is not.
83
84 *#*
85# Same as "*", but search backward. The pound sign
86 (character 163) also works. If the "#" key works as
87 backspace, try using "stty erase <BS>" before starting
88 Vim (<BS> is CTRL-H or a real backspace). {not in Vi}
89
90 *gstar*
91g* Like "*", but don't put "\<" and "\>" around the word.
92 This makes the search also find matches that are not a
93 whole word. {not in Vi}
94
95 *g#*
96g# Like "#", but don't put "\<" and "\>" around the word.
97 This makes the search also find matches that are not a
98 whole word. {not in Vi}
99
100 *gd*
101gd Goto local Declaration. When the cursor is on a local
102 variable, this command will jump to its declaration.
103 First Vim searches for the start of the current
104 function, just like "[[". If it is not found the
105 search stops in line 1. If it is found, Vim goes back
106 until a blank line is found. From this position Vim
107 searches for the keyword under the cursor, like with
108 "*", but lines that look like a comment are ignored
109 (see 'comments' option).
110 Note that this is not guaranteed to work, Vim does not
111 really check the syntax, it only searches for a match
112 with the keyword. If included files also need to be
113 searched use the commands listed in |include-search|.
114 After this command |n| searches forward for the next
115 match (not backward).
116 {not in Vi}
117
118 *gD*
119gD Goto global Declaration. When the cursor is on a
120 global variable that is defined in the file, this
121 command will jump to its declaration. This works just
122 like "gd", except that the search for the keyword
123 always starts in line 1. {not in Vi}
124
Bram Moolenaarf75a9632005-09-13 21:20:47 +0000125 *1gd*
1261gd Like "gd", but ignore matches inside a {} block that
127 ends before the cursor position. {not in Vi}
128
129 *1gD*
1301gD Like "gD", but ignore matches inside a {} block that
131 ends before the cursor position. {not in Vi}
132
Bram Moolenaar071d4272004-06-13 20:20:40 +0000133 *CTRL-C*
134CTRL-C Interrupt current (search) command. Use CTRL-Break on
135 MS-DOS |dos-CTRL-Break|.
136 In Normal mode, any pending command is aborted.
137
138 *:noh* *:nohlsearch*
139:noh[lsearch] Stop the highlighting for the 'hlsearch' option. It
140 is automatically turned back on when using a search
141 command, or setting the 'hlsearch' option.
142 This command doesn't work in an autocommand, because
143 the highlighting state is saved and restored when
144 executing autocommands |autocmd-searchpat|.
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000145 Same thing for when invoking a user function.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000146
147While typing the search pattern the current match will be shown if the
148'incsearch' option is on. Remember that you still have to finish the search
149command with <CR> to actually position the cursor at the displayed match. Or
150use <Esc> to abandon the search.
151
152All matches for the last used search pattern will be highlighted if you set
153the 'hlsearch' option. This can be suspended with the |:nohlsearch| command.
154
Bram Moolenaar15146672011-10-20 22:22:38 +0200155When no match is found you get the error: *E486* Pattern not found
156Note that for the |:global| command this behaves like a normal message, for Vi
157compatibility. For the |:s| command the "e" flag can be used to avoid the
158error message |:s_flags|.
159
Bram Moolenaar071d4272004-06-13 20:20:40 +0000160 *search-offset* *{offset}*
161These commands search for the specified pattern. With "/" and "?" an
162additional offset may be given. There are two types of offsets: line offsets
163and character offsets. {the character offsets are not in Vi}
164
165The offset gives the cursor position relative to the found match:
166 [num] [num] lines downwards, in column 1
167 +[num] [num] lines downwards, in column 1
168 -[num] [num] lines upwards, in column 1
169 e[+num] [num] characters to the right of the end of the match
170 e[-num] [num] characters to the left of the end of the match
171 s[+num] [num] characters to the right of the start of the match
172 s[-num] [num] characters to the left of the start of the match
173 b[+num] [num] identical to s[+num] above (mnemonic: begin)
174 b[-num] [num] identical to s[-num] above (mnemonic: begin)
Bram Moolenaar1d2ba7f2006-02-14 22:29:30 +0000175 ;{pattern} perform another search, see |//;|
Bram Moolenaar071d4272004-06-13 20:20:40 +0000176
177If a '-' or '+' is given but [num] is omitted, a count of one will be used.
178When including an offset with 'e', the search becomes inclusive (the
179character the cursor lands on is included in operations).
180
181Examples:
182
183pattern cursor position ~
184/test/+1 one line below "test", in column 1
185/test/e on the last t of "test"
186/test/s+2 on the 's' of "test"
187/test/b-3 three characters before "test"
188
189If one of these commands is used after an operator, the characters between
190the cursor position before and after the search is affected. However, if a
191line offset is given, the whole lines between the two cursor positions are
192affected.
193
194An example of how to search for matches with a pattern and change the match
195with another word: >
196 /foo<CR> find "foo"
Bram Moolenaar92dff182014-02-11 19:15:50 +0100197 c//e<CR> change until end of match
Bram Moolenaar071d4272004-06-13 20:20:40 +0000198 bar<Esc> type replacement
199 //<CR> go to start of next match
Bram Moolenaar92dff182014-02-11 19:15:50 +0100200 c//e<CR> change until end of match
Bram Moolenaar071d4272004-06-13 20:20:40 +0000201 beep<Esc> type another replacement
202 etc.
203<
204 *//;* *E386*
205A very special offset is ';' followed by another search command. For example: >
206
207 /test 1/;/test
208 /test.*/+1;?ing?
209
210The first one first finds the next occurrence of "test 1", and then the first
211occurrence of "test" after that.
212
213This is like executing two search commands after each other, except that:
214- It can be used as a single motion command after an operator.
215- The direction for a following "n" or "N" command comes from the first
216 search command.
217- When an error occurs the cursor is not moved at all.
218
219 *last-pattern*
220The last used pattern and offset are remembered. They can be used to repeat
221the search, possibly in another direction or with another count. Note that
222two patterns are remembered: One for 'normal' search commands and one for the
223substitute command ":s". Each time an empty pattern is given, the previously
Bram Moolenaar662db672011-03-22 14:05:35 +0100224used pattern is used. However, if there is no previous search command, a
225previous substitute pattern is used, if possible.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000226
227The 'magic' option sticks with the last used pattern. If you change 'magic',
228this will not change how the last used pattern will be interpreted.
229The 'ignorecase' option does not do this. When 'ignorecase' is changed, it
230will result in the pattern to match other text.
231
232All matches for the last used search pattern will be highlighted if you set
233the 'hlsearch' option.
234
235To clear the last used search pattern: >
236 :let @/ = ""
237This will not set the pattern to an empty string, because that would match
238everywhere. The pattern is really cleared, like when starting Vim.
239
Bram Moolenaar8f999f12005-01-25 22:12:55 +0000240The search usually skips matches that don't move the cursor. Whether the next
Bram Moolenaar071d4272004-06-13 20:20:40 +0000241match is found at the next character or after the skipped match depends on the
242'c' flag in 'cpoptions'. See |cpo-c|.
243 with 'c' flag: "/..." advances 1 to 3 characters
244 without 'c' flag: "/..." advances 1 character
245The unpredictability with the 'c' flag is caused by starting the search in the
246first column, skipping matches until one is found past the cursor position.
247
Bram Moolenaar8f999f12005-01-25 22:12:55 +0000248When searching backwards, searching starts at the start of the line, using the
249'c' flag in 'cpoptions' as described above. Then the last match before the
250cursor position is used.
251
Bram Moolenaar071d4272004-06-13 20:20:40 +0000252In Vi the ":tag" command sets the last search pattern when the tag is searched
253for. In Vim this is not done, the previous search pattern is still remembered,
254unless the 't' flag is present in 'cpoptions'. The search pattern is always
255put in the search history.
256
257If the 'wrapscan' option is on (which is the default), searches wrap around
258the end of the buffer. If 'wrapscan' is not set, the backward search stops
259at the beginning and the forward search stops at the end of the buffer. If
260'wrapscan' is set and the pattern was not found the error message "pattern
261not found" is given, and the cursor will not be moved. If 'wrapscan' is not
262set the message becomes "search hit BOTTOM without match" when searching
263forward, or "search hit TOP without match" when searching backward. If
264wrapscan is set and the search wraps around the end of the file the message
265"search hit TOP, continuing at BOTTOM" or "search hit BOTTOM, continuing at
266TOP" is given when searching backwards or forwards respectively. This can be
267switched off by setting the 's' flag in the 'shortmess' option. The highlight
268method 'w' is used for this message (default: standout).
269
270 *search-range*
Bram Moolenaar4770d092006-01-12 23:22:24 +0000271You can limit the search command "/" to a certain range of lines by including
272\%>l items. For example, to match the word "limit" below line 199 and above
273line 300: >
274 /\%>199l\%<300llimit
275Also see |/\%>l|.
276
277Another way is to use the ":substitute" command with the 'c' flag. Example: >
Bram Moolenaar071d4272004-06-13 20:20:40 +0000278 :.,300s/Pattern//gc
279This command will search from the cursor position until line 300 for
280"Pattern". At the match, you will be asked to type a character. Type 'q' to
281stop at this match, type 'n' to find the next match.
282
283The "*", "#", "g*" and "g#" commands look for a word near the cursor in this
284order, the first one that is found is used:
285- The keyword currently under the cursor.
286- The first keyword to the right of the cursor, in the same line.
287- The WORD currently under the cursor.
288- The first WORD to the right of the cursor, in the same line.
289The keyword may only contain letters and characters in 'iskeyword'.
290The WORD may contain any non-blanks (<Tab>s and/or <Space>s).
291Note that if you type with ten fingers, the characters are easy to remember:
292the "#" is under your left hand middle finger (search to the left and up) and
293the "*" is under your right hand middle finger (search to the right and down).
294(this depends on your keyboard layout though).
295
296==============================================================================
2972. The definition of a pattern *search-pattern* *pattern* *[pattern]*
298 *regular-expression* *regexp* *Pattern*
Bram Moolenaarf1f8bc52005-03-07 23:20:08 +0000299 *E76* *E383* *E476*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000300
301For starters, read chapter 27 of the user manual |usr_27.txt|.
302
303 */bar* */\bar* */pattern*
3041. A pattern is one or more branches, separated by "\|". It matches anything
305 that matches one of the branches. Example: "foo\|beep" matches "foo" and
306 matches "beep". If more than one branch matches, the first one is used.
307
308 pattern ::= branch
309 or branch \| branch
310 or branch \| branch \| branch
311 etc.
312
313 */branch* */\&*
3142. A branch is one or more concats, separated by "\&". It matches the last
315 concat, but only if all the preceding concats also match at the same
316 position. Examples:
317 "foobeep\&..." matches "foo" in "foobeep".
318 ".*Peter\&.*Bob" matches in a line containing both "Peter" and "Bob"
319
320 branch ::= concat
321 or concat \& concat
322 or concat \& concat \& concat
323 etc.
324
325 */concat*
3263. A concat is one or more pieces, concatenated. It matches a match for the
327 first piece, followed by a match for the second piece, etc. Example:
328 "f[0-9]b", first matches "f", then a digit and then "b".
329
330 concat ::= piece
331 or piece piece
332 or piece piece piece
333 etc.
334
335 */piece*
3364. A piece is an atom, possibly followed by a multi, an indication of how many
337 times the atom can be matched. Example: "a*" matches any sequence of "a"
338 characters: "", "a", "aa", etc. See |/multi|.
339
340 piece ::= atom
341 or atom multi
342
343 */atom*
3445. An atom can be one of a long list of items. Many atoms match one character
345 in the text. It is often an ordinary character or a character class.
346 Braces can be used to make a pattern into an atom. The "\z(\)" construct
347 is only for syntax highlighting.
348
349 atom ::= ordinary-atom |/ordinary-atom|
350 or \( pattern \) |/\(|
351 or \%( pattern \) |/\%(|
352 or \z( pattern \) |/\z(|
353
354
Bram Moolenaar913df812013-07-06 15:44:11 +0200355 */\%#=* *two-engines* *NFA*
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200356Vim includes two regexp engines:
3571. An old, backtracking engine that supports everything.
3582. A new, NFA engine that works much faster on some patterns, but does not
359 support everything.
360
361Vim will automatically select the right engine for you. However, if you run
362into a problem or want to specifically select one engine or the other, you can
363prepend one of the following to the pattern:
364
365 \%#=0 Force automatic selection. Only has an effect when
366 'regexpengine' has been set to a non-zero value.
367 \%#=1 Force using the old engine.
368 \%#=2 Force using the NFA engine.
369
370You can also use the 'regexpengine' option to change the default.
371
372 *E864* *E868* *E874* *E875* *E876* *E877* *E878*
373If selecting the NFA engine and it runs into something that is not implemented
374the pattern will not match. This is only useful when debugging Vim.
375
Bram Moolenaar071d4272004-06-13 20:20:40 +0000376==============================================================================
Bram Moolenaareb3593b2006-04-22 22:33:57 +00003773. Magic */magic*
378
379Some characters in the pattern are taken literally. They match with the same
380character in the text. When preceded with a backslash however, these
381characters get a special meaning.
382
383Other characters have a special meaning without a backslash. They need to be
384preceded with a backslash to match literally.
385
386If a character is taken literally or not depends on the 'magic' option and the
387items mentioned next.
388 */\m* */\M*
389Use of "\m" makes the pattern after it be interpreted as if 'magic' is set,
390ignoring the actual value of the 'magic' option.
391Use of "\M" makes the pattern after it be interpreted as if 'nomagic' is used.
392 */\v* */\V*
393Use of "\v" means that in the pattern after it all ASCII characters except
394'0'-'9', 'a'-'z', 'A'-'Z' and '_' have a special meaning. "very magic"
395
Bram Moolenaar256972a2015-12-29 19:10:25 +0100396Use of "\V" means that in the pattern after it only the backslash and the
397terminating character (/ or ?) has a special meaning. "very nomagic"
Bram Moolenaareb3593b2006-04-22 22:33:57 +0000398
399Examples:
400after: \v \m \M \V matches ~
401 'magic' 'nomagic'
402 $ $ $ \$ matches end-of-line
403 . . \. \. matches any character
404 * * \* \* any number of the previous atom
Bram Moolenaar256972a2015-12-29 19:10:25 +0100405 ~ ~ \~ \~ latest substitute string
Bram Moolenaareb3593b2006-04-22 22:33:57 +0000406 () \(\) \(\) \(\) grouping into an atom
407 | \| \| \| separating alternatives
408 \a \a \a \a alphabetic character
409 \\ \\ \\ \\ literal backslash
410 \. \. . . literal dot
411 \{ { { { literal '{'
412 a a a a literal 'a'
413
414{only Vim supports \m, \M, \v and \V}
415
416It is recommended to always keep the 'magic' option at the default setting,
417which is 'magic'. This avoids portability problems. To make a pattern immune
418to the 'magic' option being set or not, put "\m" or "\M" at the start of the
419pattern.
420
421==============================================================================
Bram Moolenaar071d4272004-06-13 20:20:40 +00004224. Overview of pattern items *pattern-overview*
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200423 *E865* *E866* *E867* *E869*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000424
425Overview of multi items. */multi* *E61* *E62*
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200426More explanation and examples below, follow the links. *E64* *E871*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000427
428 multi ~
429 'magic' 'nomagic' matches of the preceding atom ~
430|/star| * \* 0 or more as many as possible
431|/\+| \+ \+ 1 or more as many as possible (*)
432|/\=| \= \= 0 or 1 as many as possible (*)
433|/\?| \? \? 0 or 1 as many as possible (*)
434
435|/\{| \{n,m} \{n,m} n to m as many as possible (*)
436 \{n} \{n} n exactly (*)
437 \{n,} \{n,} at least n as many as possible (*)
438 \{,m} \{,m} 0 to m as many as possible (*)
439 \{} \{} 0 or more as many as possible (same as *) (*)
440
441|/\{-| \{-n,m} \{-n,m} n to m as few as possible (*)
442 \{-n} \{-n} n exactly (*)
443 \{-n,} \{-n,} at least n as few as possible (*)
444 \{-,m} \{-,m} 0 to m as few as possible (*)
445 \{-} \{-} 0 or more as few as possible (*)
446
447 *E59*
448|/\@>| \@> \@> 1, like matching a whole pattern (*)
449|/\@=| \@= \@= nothing, requires a match |/zero-width| (*)
450|/\@!| \@! \@! nothing, requires NO match |/zero-width| (*)
451|/\@<=| \@<= \@<= nothing, requires a match behind |/zero-width| (*)
452|/\@<!| \@<! \@<! nothing, requires NO match behind |/zero-width| (*)
453
454(*) {not in Vi}
455
456
457Overview of ordinary atoms. */ordinary-atom*
458More explanation and examples below, follow the links.
459
460 ordinary atom ~
461 magic nomagic matches ~
462|/^| ^ ^ start-of-line (at start of pattern) |/zero-width|
463|/\^| \^ \^ literal '^'
464|/\_^| \_^ \_^ start-of-line (used anywhere) |/zero-width|
465|/$| $ $ end-of-line (at end of pattern) |/zero-width|
466|/\$| \$ \$ literal '$'
467|/\_$| \_$ \_$ end-of-line (used anywhere) |/zero-width|
468|/.| . \. any single character (not an end-of-line)
469|/\_.| \_. \_. any single character or end-of-line
470|/\<| \< \< beginning of a word |/zero-width|
471|/\>| \> \> end of a word |/zero-width|
472|/\zs| \zs \zs anything, sets start of match
473|/\ze| \ze \ze anything, sets end of match
474|/\%^| \%^ \%^ beginning of file |/zero-width| *E71*
475|/\%$| \%$ \%$ end of file |/zero-width|
Bram Moolenaar33aec762006-01-22 23:30:12 +0000476|/\%V| \%V \%V inside Visual area |/zero-width|
Bram Moolenaar071d4272004-06-13 20:20:40 +0000477|/\%#| \%# \%# cursor position |/zero-width|
Bram Moolenaar33aec762006-01-22 23:30:12 +0000478|/\%'m| \%'m \%'m mark m position |/zero-width|
Bram Moolenaar071d4272004-06-13 20:20:40 +0000479|/\%l| \%23l \%23l in line 23 |/zero-width|
480|/\%c| \%23c \%23c in column 23 |/zero-width|
481|/\%v| \%23v \%23v in virtual column 23 |/zero-width|
482
Bram Moolenaar5eb86f92004-07-26 12:53:41 +0000483Character classes {not in Vi}: */character-classes*
Bram Moolenaar256972a2015-12-29 19:10:25 +0100484 magic nomagic matches ~
Bram Moolenaar071d4272004-06-13 20:20:40 +0000485|/\i| \i \i identifier character (see 'isident' option)
486|/\I| \I \I like "\i", but excluding digits
487|/\k| \k \k keyword character (see 'iskeyword' option)
488|/\K| \K \K like "\k", but excluding digits
489|/\f| \f \f file name character (see 'isfname' option)
490|/\F| \F \F like "\f", but excluding digits
491|/\p| \p \p printable character (see 'isprint' option)
492|/\P| \P \P like "\p", but excluding digits
493|/\s| \s \s whitespace character: <Space> and <Tab>
494|/\S| \S \S non-whitespace character; opposite of \s
495|/\d| \d \d digit: [0-9]
496|/\D| \D \D non-digit: [^0-9]
497|/\x| \x \x hex digit: [0-9A-Fa-f]
498|/\X| \X \X non-hex digit: [^0-9A-Fa-f]
499|/\o| \o \o octal digit: [0-7]
500|/\O| \O \O non-octal digit: [^0-7]
501|/\w| \w \w word character: [0-9A-Za-z_]
502|/\W| \W \W non-word character: [^0-9A-Za-z_]
503|/\h| \h \h head of word character: [A-Za-z_]
504|/\H| \H \H non-head of word character: [^A-Za-z_]
505|/\a| \a \a alphabetic character: [A-Za-z]
506|/\A| \A \A non-alphabetic character: [^A-Za-z]
507|/\l| \l \l lowercase character: [a-z]
508|/\L| \L \L non-lowercase character: [^a-z]
509|/\u| \u \u uppercase character: [A-Z]
510|/\U| \U \U non-uppercase character [^A-Z]
511|/\_| \_x \_x where x is any of the characters above: character
512 class with end-of-line included
513(end of character classes)
514
Bram Moolenaar256972a2015-12-29 19:10:25 +0100515 magic nomagic matches ~
Bram Moolenaar071d4272004-06-13 20:20:40 +0000516|/\e| \e \e <Esc>
517|/\t| \t \t <Tab>
518|/\r| \r \r <CR>
519|/\b| \b \b <BS>
520|/\n| \n \n end-of-line
521|/~| ~ \~ last given substitute string
522|/\1| \1 \1 same string as matched by first \(\) {not in Vi}
523|/\2| \2 \2 Like "\1", but uses second \(\)
524 ...
525|/\9| \9 \9 Like "\1", but uses ninth \(\)
526 *E68*
527|/\z1| \z1 \z1 only for syntax highlighting, see |:syn-ext-match|
528 ...
529|/\z1| \z9 \z9 only for syntax highlighting, see |:syn-ext-match|
530
531 x x a character with no special meaning matches itself
532
533|/[]| [] \[] any character specified inside the []
Bram Moolenaar00154502013-02-13 16:15:55 +0100534|/\%[]| \%[] \%[] a sequence of optionally matched atoms
Bram Moolenaar071d4272004-06-13 20:20:40 +0000535
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000536|/\c| \c \c ignore case, do not use the 'ignorecase' option
537|/\C| \C \C match case, do not use the 'ignorecase' option
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200538|/\Z| \Z \Z ignore differences in Unicode "combining characters".
539 Useful when searching voweled Hebrew or Arabic text.
540
Bram Moolenaar256972a2015-12-29 19:10:25 +0100541 magic nomagic matches ~
Bram Moolenaar071d4272004-06-13 20:20:40 +0000542|/\m| \m \m 'magic' on for the following chars in the pattern
543|/\M| \M \M 'magic' off for the following chars in the pattern
544|/\v| \v \v the following chars in the pattern are "very magic"
545|/\V| \V \V the following chars in the pattern are "very nomagic"
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200546|/\%#=| \%#=1 \%#=1 select regexp engine |/zero-width|
Bram Moolenaar071d4272004-06-13 20:20:40 +0000547
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +0100548|/\%d| \%d \%d match specified decimal character (eg \%d123)
Bram Moolenaarc0197e22004-09-13 20:26:32 +0000549|/\%x| \%x \%x match specified hex character (eg \%x2a)
550|/\%o| \%o \%o match specified octal character (eg \%o040)
551|/\%u| \%u \%u match specified multibyte character (eg \%u20ac)
552|/\%U| \%U \%U match specified large multibyte character (eg
553 \%U12345678)
Bram Moolenaar8df5acf2014-05-13 19:37:29 +0200554|/\%C| \%C \%C match any composing characters
Bram Moolenaar071d4272004-06-13 20:20:40 +0000555
556Example matches ~
557\<\I\i* or
558\<\h\w*
559\<[a-zA-Z_][a-zA-Z0-9_]*
560 An identifier (e.g., in a C program).
561
562\(\.$\|\. \) A period followed by <EOL> or a space.
563
564[.!?][])"']*\($\|[ ]\) A search pattern that finds the end of a sentence,
565 with almost the same definition as the ")" command.
566
567cat\Z Both "cat" and "càt" ("a" followed by 0x0300)
568 Does not match "càt" (character 0x00e0), even
569 though it may look the same.
570
571
572==============================================================================
Bram Moolenaar071d4272004-06-13 20:20:40 +00005735. Multi items *pattern-multi-items*
574
575An atom can be followed by an indication of how many times the atom can be
576matched and in what way. This is called a multi. See |/multi| for an
577overview.
578
Bram Moolenaar071d4272004-06-13 20:20:40 +0000579 */star* */\star* *E56*
580* (use \* when 'magic' is not set)
581 Matches 0 or more of the preceding atom, as many as possible.
582 Example 'nomagic' matches ~
583 a* a\* "", "a", "aa", "aaa", etc.
584 .* \.\* anything, also an empty string, no end-of-line
585 \_.* \_.\* everything up to the end of the buffer
586 \_.*END \_.\*END everything up to and including the last "END"
587 in the buffer
588
589 Exception: When "*" is used at the start of the pattern or just after
590 "^" it matches the star character.
591
592 Be aware that repeating "\_." can match a lot of text and take a long
593 time. For example, "\_.*END" matches all text from the current
594 position to the last occurrence of "END" in the file. Since the "*"
595 will match as many as possible, this first skips over all lines until
596 the end of the file and then tries matching "END", backing up one
597 character at a time.
598
599 */\+* *E57*
600\+ Matches 1 or more of the preceding atom, as many as possible. {not in
601 Vi}
602 Example matches ~
603 ^.\+$ any non-empty line
604 \s\+ white space of at least one character
605
606 */\=*
607\= Matches 0 or 1 of the preceding atom, as many as possible. {not in Vi}
608 Example matches ~
609 foo\= "fo" and "foo"
610
611 */\?*
612\? Just like \=. Cannot be used when searching backwards with the "?"
613 command. {not in Vi}
614
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200615 */\{* *E58* *E60* *E554* *E870*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000616\{n,m} Matches n to m of the preceding atom, as many as possible
617\{n} Matches n of the preceding atom
618\{n,} Matches at least n of the preceding atom, as many as possible
619\{,m} Matches 0 to m of the preceding atom, as many as possible
620\{} Matches 0 or more of the preceding atom, as many as possible (like *)
621 */\{-*
622\{-n,m} matches n to m of the preceding atom, as few as possible
623\{-n} matches n of the preceding atom
624\{-n,} matches at least n of the preceding atom, as few as possible
625\{-,m} matches 0 to m of the preceding atom, as few as possible
626\{-} matches 0 or more of the preceding atom, as few as possible
627 {Vi does not have any of these}
628
Bram Moolenaar26a60b42005-02-22 08:49:11 +0000629 n and m are positive decimal numbers or zero
Bram Moolenaarc81e5e72007-05-05 18:24:42 +0000630 *non-greedy*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000631 If a "-" appears immediately after the "{", then a shortest match
632 first algorithm is used (see example below). In particular, "\{-}" is
633 the same as "*" but uses the shortest match first algorithm. BUT: A
634 match that starts earlier is preferred over a shorter match: "a\{-}b"
635 matches "aaab" in "xaaab".
636
637 Example matches ~
638 ab\{2,3}c "abbc" or "abbbc"
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000639 a\{5} "aaaaa"
640 ab\{2,}c "abbc", "abbbc", "abbbbc", etc.
641 ab\{,3}c "ac", "abc", "abbc" or "abbbc"
Bram Moolenaar071d4272004-06-13 20:20:40 +0000642 a[bc]\{3}d "abbbd", "abbcd", "acbcd", "acccd", etc.
643 a\(bc\)\{1,2}d "abcd" or "abcbcd"
644 a[bc]\{-}[cd] "abc" in "abcd"
645 a[bc]*[cd] "abcd" in "abcd"
646
647 The } may optionally be preceded with a backslash: \{n,m\}.
648
649 */\@=*
650\@= Matches the preceding atom with zero width. {not in Vi}
651 Like "(?=pattern)" in Perl.
652 Example matches ~
653 foo\(bar\)\@= "foo" in "foobar"
654 foo\(bar\)\@=foo nothing
655 */zero-width*
656 When using "\@=" (or "^", "$", "\<", "\>") no characters are included
657 in the match. These items are only used to check if a match can be
658 made. This can be tricky, because a match with following items will
659 be done in the same position. The last example above will not match
660 "foobarfoo", because it tries match "foo" in the same position where
661 "bar" matched.
662
663 Note that using "\&" works the same as using "\@=": "foo\&.." is the
664 same as "\(foo\)\@=..". But using "\&" is easier, you don't need the
665 braces.
666
667
668 */\@!*
669\@! Matches with zero width if the preceding atom does NOT match at the
670 current position. |/zero-width| {not in Vi}
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200671 Like "(?!pattern)" in Perl.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000672 Example matches ~
673 foo\(bar\)\@! any "foo" not followed by "bar"
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200674 a.\{-}p\@! "a", "ap", "app", "appp", etc. not immediately
Bram Moolenaar251e1912011-06-19 05:09:16 +0200675 followed by a "p"
Bram Moolenaar071d4272004-06-13 20:20:40 +0000676 if \(\(then\)\@!.\)*$ "if " not followed by "then"
677
678 Using "\@!" is tricky, because there are many places where a pattern
679 does not match. "a.*p\@!" will match from an "a" to the end of the
680 line, because ".*" can match all characters in the line and the "p"
681 doesn't match at the end of the line. "a.\{-}p\@!" will match any
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200682 "a", "ap", "app", etc. that isn't followed by a "p", because the "."
Bram Moolenaar071d4272004-06-13 20:20:40 +0000683 can match a "p" and "p\@!" doesn't match after that.
684
685 You can't use "\@!" to look for a non-match before the matching
686 position: "\(foo\)\@!bar" will match "bar" in "foobar", because at the
687 position where "bar" matches, "foo" does not match. To avoid matching
688 "foobar" you could use "\(foo\)\@!...bar", but that doesn't match a
Bram Moolenaar13fcaaf2005-04-15 21:13:42 +0000689 bar at the start of a line. Use "\(foo\)\@<!bar".
Bram Moolenaar071d4272004-06-13 20:20:40 +0000690
Bram Moolenaar8e5af3e2011-04-28 19:02:44 +0200691 Useful example: to find "foo" in a line that does not contain "bar": >
692 /^\%(.*bar\)\@!.*\zsfoo
693< This pattern first checks that there is not a single position in the
694 line where "bar" matches. If ".*bar" matches somewhere the \@! will
695 reject the pattern. When there is no match any "foo" will be found.
696 The "\zs" is to have the match start just before "foo".
697
Bram Moolenaar071d4272004-06-13 20:20:40 +0000698 */\@<=*
699\@<= Matches with zero width if the preceding atom matches just before what
700 follows. |/zero-width| {not in Vi}
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200701 Like "(?<=pattern)" in Perl, but Vim allows non-fixed-width patterns.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000702 Example matches ~
703 \(an\_s\+\)\@<=file "file" after "an" and white space or an
704 end-of-line
705 For speed it's often much better to avoid this multi. Try using "\zs"
706 instead |/\zs|. To match the same as the above example:
707 an\_s\+\zsfile
Bram Moolenaar543b7ef2013-06-01 14:50:56 +0200708 At least set a limit for the look-behind, see below.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000709
710 "\@<=" and "\@<!" check for matches just before what follows.
711 Theoretically these matches could start anywhere before this position.
712 But to limit the time needed, only the line where what follows matches
713 is searched, and one line before that (if there is one). This should
714 be sufficient to match most things and not be too slow.
Bram Moolenaarfb539272014-08-22 19:21:47 +0200715
716 In the old regexp engine the part of the pattern after "\@<=" and
717 "\@<!" are checked for a match first, thus things like "\1" don't work
718 to reference \(\) inside the preceding atom. It does work the other
719 way around:
720 Bad example matches ~
721 \%#=1\1\@<=,\([a-z]\+\) ",abc" in "abc,abc"
722
723 However, the new regexp engine works differently, it is better to not
724 rely on this behavior, do not use \@<= if it can be avoided:
725 Example matches ~
726 \([a-z]\+\)\zs,\1 ",abc" in "abc,abc"
Bram Moolenaar071d4272004-06-13 20:20:40 +0000727
Bram Moolenaar543b7ef2013-06-01 14:50:56 +0200728\@123<=
729 Like "\@<=" but only look back 123 bytes. This avoids trying lots
730 of matches that are known to fail and make executing the pattern very
731 slow. Example, check if there is a "<" just before "span":
732 /<\@1<=span
733 This will try matching "<" only one byte before "span", which is the
734 only place that works anyway.
735 After crossing a line boundary, the limit is relative to the end of
736 the line. Thus the characters at the start of the line with the match
737 are not counted (this is just to keep it simple).
738 The number zero is the same as no limit.
739
Bram Moolenaar071d4272004-06-13 20:20:40 +0000740 */\@<!*
741\@<! Matches with zero width if the preceding atom does NOT match just
742 before what follows. Thus this matches if there is no position in the
743 current or previous line where the atom matches such that it ends just
744 before what follows. |/zero-width| {not in Vi}
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200745 Like "(?<!pattern)" in Perl, but Vim allows non-fixed-width patterns.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000746 The match with the preceding atom is made to end just before the match
747 with what follows, thus an atom that ends in ".*" will work.
748 Warning: This can be slow (because many positions need to be checked
Bram Moolenaar543b7ef2013-06-01 14:50:56 +0200749 for a match). Use a limit if you can, see below.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000750 Example matches ~
751 \(foo\)\@<!bar any "bar" that's not in "foobar"
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000752 \(\/\/.*\)\@<!in "in" which is not after "//"
Bram Moolenaar071d4272004-06-13 20:20:40 +0000753
Bram Moolenaar543b7ef2013-06-01 14:50:56 +0200754\@123<!
755 Like "\@<!" but only look back 123 bytes. This avoids trying lots of
756 matches that are known to fail and make executing the pattern very
757 slow.
758
Bram Moolenaar071d4272004-06-13 20:20:40 +0000759 */\@>*
760\@> Matches the preceding atom like matching a whole pattern. {not in Vi}
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000761 Like "(?>pattern)" in Perl.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000762 Example matches ~
763 \(a*\)\@>a nothing (the "a*" takes all the "a"'s, there can't be
764 another one following)
765
766 This matches the preceding atom as if it was a pattern by itself. If
767 it doesn't match, there is no retry with shorter sub-matches or
768 anything. Observe this difference: "a*b" and "a*ab" both match
769 "aaab", but in the second case the "a*" matches only the first two
770 "a"s. "\(a*\)\@>ab" will not match "aaab", because the "a*" matches
771 the "aaa" (as many "a"s as possible), thus the "ab" can't match.
772
773
774==============================================================================
7756. Ordinary atoms *pattern-atoms*
776
777An ordinary atom can be:
778
779 */^*
780^ At beginning of pattern or after "\|", "\(", "\%(" or "\n": matches
781 start-of-line; at other positions, matches literal '^'. |/zero-width|
782 Example matches ~
783 ^beep( the start of the C function "beep" (probably).
784
785 */\^*
786\^ Matches literal '^'. Can be used at any position in the pattern.
787
788 */\_^*
789\_^ Matches start-of-line. |/zero-width| Can be used at any position in
790 the pattern.
791 Example matches ~
792 \_s*\_^foo white space and blank lines and then "foo" at
793 start-of-line
794
795 */$*
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000796$ At end of pattern or in front of "\|", "\)" or "\n" ('magic' on):
Bram Moolenaar071d4272004-06-13 20:20:40 +0000797 matches end-of-line <EOL>; at other positions, matches literal '$'.
798 |/zero-width|
799
800 */\$*
801\$ Matches literal '$'. Can be used at any position in the pattern.
802
803 */\_$*
804\_$ Matches end-of-line. |/zero-width| Can be used at any position in the
805 pattern. Note that "a\_$b" never matches, since "b" cannot match an
806 end-of-line. Use "a\nb" instead |/\n|.
807 Example matches ~
808 foo\_$\_s* "foo" at end-of-line and following white space and
809 blank lines
810
811. (with 'nomagic': \.) */.* */\.*
812 Matches any single character, but not an end-of-line.
813
814 */\_.*
815\_. Matches any single character or end-of-line.
816 Careful: "\_.*" matches all text to the end of the buffer!
817
818 */\<*
819\< Matches the beginning of a word: The next char is the first char of a
820 word. The 'iskeyword' option specifies what is a word character.
821 |/zero-width|
822
823 */\>*
824\> Matches the end of a word: The previous char is the last char of a
Bram Moolenaar13fcaaf2005-04-15 21:13:42 +0000825 word. The 'iskeyword' option specifies what is a word character.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000826 |/zero-width|
827
828 */\zs*
829\zs Matches at any position, and sets the start of the match there: The
830 next char is the first char of the whole match. |/zero-width|
831 Example: >
832 /^\s*\zsif
833< matches an "if" at the start of a line, ignoring white space.
834 Can be used multiple times, the last one encountered in a matching
Bram Moolenaar13fcaaf2005-04-15 21:13:42 +0000835 branch is used. Example: >
Bram Moolenaar071d4272004-06-13 20:20:40 +0000836 /\(.\{-}\zsFab\)\{3}
837< Finds the third occurrence of "Fab".
Bram Moolenaar34401cc2014-08-29 15:12:19 +0200838 This cannot be followed by a multi. *E888*
Bram Moolenaardb84e452010-08-15 13:50:43 +0200839 {not in Vi} {not available when compiled without the |+syntax| feature}
Bram Moolenaar071d4272004-06-13 20:20:40 +0000840 */\ze*
841\ze Matches at any position, and sets the end of the match there: The
842 previous char is the last char of the whole match. |/zero-width|
843 Can be used multiple times, the last one encountered in a matching
844 branch is used.
845 Example: "end\ze\(if\|for\)" matches the "end" in "endif" and
846 "endfor".
Bram Moolenaar6e932462014-09-09 18:48:09 +0200847 This cannot be followed by a multi. |E888|
Bram Moolenaardb84e452010-08-15 13:50:43 +0200848 {not in Vi} {not available when compiled without the |+syntax| feature}
Bram Moolenaar071d4272004-06-13 20:20:40 +0000849
850 */\%^* *start-of-file*
851\%^ Matches start of the file. When matching with a string, matches the
852 start of the string. {not in Vi}
853 For example, to find the first "VIM" in a file: >
854 /\%^\_.\{-}\zsVIM
855<
856 */\%$* *end-of-file*
857\%$ Matches end of the file. When matching with a string, matches the
858 end of the string. {not in Vi}
859 Note that this does NOT find the last "VIM" in a file: >
860 /VIM\_.\{-}\%$
861< It will find the next VIM, because the part after it will always
862 match. This one will find the last "VIM" in the file: >
863 /VIM\ze\(\(VIM\)\@!\_.\)*\%$
864< This uses |/\@!| to ascertain that "VIM" does NOT match in any
865 position after the first "VIM".
866 Searching from the end of the file backwards is easier!
867
Bram Moolenaar33aec762006-01-22 23:30:12 +0000868 */\%V*
869\%V Match inside the Visual area. When Visual mode has already been
870 stopped match in the area that |gv| would reselect.
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +0100871 This is a |/zero-width| match. To make sure the whole pattern is
872 inside the Visual area put it at the start and end of the pattern,
873 e.g.: >
874 /\%Vfoo.*bar\%V
875< Only works for the current buffer.
Bram Moolenaar33aec762006-01-22 23:30:12 +0000876
Bram Moolenaar071d4272004-06-13 20:20:40 +0000877 */\%#* *cursor-position*
878\%# Matches with the cursor position. Only works when matching in a
879 buffer displayed in a window. {not in Vi}
880 WARNING: When the cursor is moved after the pattern was used, the
881 result becomes invalid. Vim doesn't automatically update the matches.
882 This is especially relevant for syntax highlighting and 'hlsearch'.
883 In other words: When the cursor moves the display isn't updated for
884 this change. An update is done for lines which are changed (the whole
885 line is updated) or when using the |CTRL-L| command (the whole screen
886 is updated). Example, to highlight the word under the cursor: >
887 /\k*\%#\k*
888< When 'hlsearch' is set and you move the cursor around and make changes
889 this will clearly show when the match is updated or not.
890
Bram Moolenaar33aec762006-01-22 23:30:12 +0000891 */\%'m* */\%<'m* */\%>'m*
892\%'m Matches with the position of mark m.
893\%<'m Matches before the position of mark m.
894\%>'m Matches after the position of mark m.
895 Example, to highlight the text from mark 's to 'e: >
896 /.\%>'s.*\%<'e..
897< Note that two dots are required to include mark 'e in the match. That
898 is because "\%<'e" matches at the character before the 'e mark, and
899 since it's a |/zero-width| match it doesn't include that character.
900 {not in Vi}
901 WARNING: When the mark is moved after the pattern was used, the result
902 becomes invalid. Vim doesn't automatically update the matches.
Bram Moolenaar1ef15e32006-02-01 21:56:25 +0000903 Similar to moving the cursor for "\%#" |/\%#|.
Bram Moolenaar33aec762006-01-22 23:30:12 +0000904
Bram Moolenaar071d4272004-06-13 20:20:40 +0000905 */\%l* */\%>l* */\%<l*
906\%23l Matches in a specific line.
Bram Moolenaar4770d092006-01-12 23:22:24 +0000907\%<23l Matches above a specific line (lower line number).
908\%>23l Matches below a specific line (higher line number).
Bram Moolenaar071d4272004-06-13 20:20:40 +0000909 These three can be used to match specific lines in a buffer. The "23"
910 can be any line number. The first line is 1. {not in Vi}
911 WARNING: When inserting or deleting lines Vim does not automatically
912 update the matches. This means Syntax highlighting quickly becomes
913 wrong.
914 Example, to highlight the line where the cursor currently is: >
915 :exe '/\%' . line(".") . 'l.*'
916< When 'hlsearch' is set and you move the cursor around and make changes
917 this will clearly show when the match is updated or not.
918
919 */\%c* */\%>c* */\%<c*
920\%23c Matches in a specific column.
921\%<23c Matches before a specific column.
922\%>23c Matches after a specific column.
923 These three can be used to match specific columns in a buffer or
924 string. The "23" can be any column number. The first column is 1.
925 Actually, the column is the byte number (thus it's not exactly right
926 for multi-byte characters). {not in Vi}
927 WARNING: When inserting or deleting text Vim does not automatically
928 update the matches. This means Syntax highlighting quickly becomes
929 wrong.
930 Example, to highlight the column where the cursor currently is: >
931 :exe '/\%' . col(".") . 'c'
932< When 'hlsearch' is set and you move the cursor around and make changes
933 this will clearly show when the match is updated or not.
934 Example for matching a single byte in column 44: >
935 /\%>43c.\%<46c
936< Note that "\%<46c" matches in column 45 when the "." matches a byte in
937 column 44.
938 */\%v* */\%>v* */\%<v*
939\%23v Matches in a specific virtual column.
940\%<23v Matches before a specific virtual column.
941\%>23v Matches after a specific virtual column.
942 These three can be used to match specific virtual columns in a buffer
943 or string. When not matching with a buffer in a window, the option
944 values of the current window are used (e.g., 'tabstop').
945 The "23" can be any column number. The first column is 1.
946 Note that some virtual column positions will never match, because they
Bram Moolenaar69c2f172007-05-12 14:57:31 +0000947 are halfway through a tab or other character that occupies more than
948 one screen character. {not in Vi}
Bram Moolenaar071d4272004-06-13 20:20:40 +0000949 WARNING: When inserting or deleting text Vim does not automatically
Bram Moolenaarde934d72005-05-22 22:09:40 +0000950 update highlighted matches. This means Syntax highlighting quickly
951 becomes wrong.
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000952 Example, to highlight all the characters after virtual column 72: >
Bram Moolenaar071d4272004-06-13 20:20:40 +0000953 /\%>72v.*
954< When 'hlsearch' is set and you move the cursor around and make changes
955 this will clearly show when the match is updated or not.
956 To match the text up to column 17: >
957 /.*\%17v
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +0100958< Column 17 is included, because that's where the "\%17v" matches,
959 even though this is a |/zero-width| match. Adding a dot to match the
960 next character has the same result: >
961 /.*\%17v.
962< This command does the same thing, but also matches when there is no
963 character in column 17: >
964 /.*\%<18v.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000965<
966
967Character classes: {not in Vi}
968\i identifier character (see 'isident' option) */\i*
969\I like "\i", but excluding digits */\I*
970\k keyword character (see 'iskeyword' option) */\k*
971\K like "\k", but excluding digits */\K*
972\f file name character (see 'isfname' option) */\f*
973\F like "\f", but excluding digits */\F*
974\p printable character (see 'isprint' option) */\p*
975\P like "\p", but excluding digits */\P*
976
977NOTE: the above also work for multi-byte characters. The ones below only
978match ASCII characters, as indicated by the range.
979
980 *whitespace* *white-space*
981\s whitespace character: <Space> and <Tab> */\s*
982\S non-whitespace character; opposite of \s */\S*
983\d digit: [0-9] */\d*
984\D non-digit: [^0-9] */\D*
985\x hex digit: [0-9A-Fa-f] */\x*
986\X non-hex digit: [^0-9A-Fa-f] */\X*
987\o octal digit: [0-7] */\o*
988\O non-octal digit: [^0-7] */\O*
989\w word character: [0-9A-Za-z_] */\w*
990\W non-word character: [^0-9A-Za-z_] */\W*
991\h head of word character: [A-Za-z_] */\h*
992\H non-head of word character: [^A-Za-z_] */\H*
993\a alphabetic character: [A-Za-z] */\a*
994\A non-alphabetic character: [^A-Za-z] */\A*
995\l lowercase character: [a-z] */\l*
996\L non-lowercase character: [^a-z] */\L*
997\u uppercase character: [A-Z] */\u*
Bram Moolenaarf1568ec2011-12-14 21:17:39 +0100998\U non-uppercase character: [^A-Z] */\U*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000999
1000 NOTE: Using the atom is faster than the [] form.
1001
1002 NOTE: 'ignorecase', "\c" and "\C" are not used by character classes.
1003
1004 */\_* *E63* */\_i* */\_I* */\_k* */\_K* */\_f* */\_F*
1005 */\_p* */\_P* */\_s* */\_S* */\_d* */\_D* */\_x* */\_X*
1006 */\_o* */\_O* */\_w* */\_W* */\_h* */\_H* */\_a* */\_A*
1007 */\_l* */\_L* */\_u* */\_U*
1008\_x Where "x" is any of the characters above: The character class with
1009 end-of-line added
1010(end of character classes)
1011
1012\e matches <Esc> */\e*
1013\t matches <Tab> */\t*
1014\r matches <CR> */\r*
1015\b matches <BS> */\b*
1016\n matches an end-of-line */\n*
1017 When matching in a string instead of buffer text a literal newline
1018 character is matched.
1019
1020~ matches the last given substitute string */~* */\~*
1021
1022\(\) A pattern enclosed by escaped parentheses. */\(* */\(\)* */\)*
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +02001023 E.g., "\(^a\)" matches 'a' at the start of a line.
1024 *E51* *E54* *E55* *E872* *E873*
Bram Moolenaar071d4272004-06-13 20:20:40 +00001025
1026\1 Matches the same string that was matched by */\1* *E65*
1027 the first sub-expression in \( and \). {not in Vi}
1028 Example: "\([a-z]\).\1" matches "ata", "ehe", "tot", etc.
1029\2 Like "\1", but uses second sub-expression, */\2*
1030 ... */\3*
1031\9 Like "\1", but uses ninth sub-expression. */\9*
1032 Note: The numbering of groups is done based on which "\(" comes first
1033 in the pattern (going left to right), NOT based on what is matched
1034 first.
1035
1036\%(\) A pattern enclosed by escaped parentheses. */\%(\)* */\%(* *E53*
1037 Just like \(\), but without counting it as a sub-expression. This
1038 allows using more groups and it's a little bit faster.
1039 {not in Vi}
1040
1041x A single character, with no special meaning, matches itself
1042
1043 */\* */\\*
1044\x A backslash followed by a single character, with no special meaning,
1045 is reserved for future expansions
1046
1047[] (with 'nomagic': \[]) */[]* */\[]* */\_[]* */collection*
1048\_[]
Bram Moolenaar13fcaaf2005-04-15 21:13:42 +00001049 A collection. This is a sequence of characters enclosed in brackets.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001050 It matches any single character in the collection.
1051 Example matches ~
1052 [xyz] any 'x', 'y' or 'z'
1053 [a-zA-Z]$ any alphabetic character at the end of a line
1054 \c[a-z]$ same
Bram Moolenaara3e6bc92013-01-30 14:18:00 +01001055 [А-яЁё] Russian alphabet (with utf-8 and cp1251)
1056
Bram Moolenaarc81e5e72007-05-05 18:24:42 +00001057 */[\n]*
Bram Moolenaar071d4272004-06-13 20:20:40 +00001058 With "\_" prepended the collection also includes the end-of-line.
1059 The same can be done by including "\n" in the collection. The
1060 end-of-line is also matched when the collection starts with "^"! Thus
1061 "\_[^ab]" matches the end-of-line and any character but "a" and "b".
1062 This makes it Vi compatible: Without the "\_" or "\n" the collection
1063 does not match an end-of-line.
Bram Moolenaar8aff23a2005-08-19 20:40:30 +00001064 *E769*
Bram Moolenaarae5bce12005-08-15 21:41:48 +00001065 When the ']' is not there Vim will not give an error message but
Bram Moolenaar8aff23a2005-08-19 20:40:30 +00001066 assume no collection is used. Useful to search for '['. However, you
Bram Moolenaar5837f1f2015-03-21 18:06:14 +01001067 do get E769 for internal searching. And be aware that in a
1068 `:substitute` command the whole command becomes the pattern. E.g.
1069 ":s/[/x/" searches for "[/x" and replaces it with nothing. It does
1070 not search for "[" and replaces it with "x"!
Bram Moolenaarae5bce12005-08-15 21:41:48 +00001071
Bram Moolenaar071d4272004-06-13 20:20:40 +00001072 If the sequence begins with "^", it matches any single character NOT
1073 in the collection: "[^xyz]" matches anything but 'x', 'y' and 'z'.
1074 - If two characters in the sequence are separated by '-', this is
1075 shorthand for the full list of ASCII characters between them. E.g.,
Bram Moolenaar0bc380a2010-07-10 13:52:13 +02001076 "[0-9]" matches any decimal digit. Non-ASCII characters can be
1077 used, but the character values must not be more than 256 apart.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001078 - A character class expression is evaluated to the set of characters
1079 belonging to that character class. The following character classes
1080 are supported:
1081 Name Contents ~
1082*[:alnum:]* [:alnum:] letters and digits
1083*[:alpha:]* [:alpha:] letters
1084*[:blank:]* [:blank:] space and tab characters
1085*[:cntrl:]* [:cntrl:] control characters
1086*[:digit:]* [:digit:] decimal digits
1087*[:graph:]* [:graph:] printable characters excluding space
1088*[:lower:]* [:lower:] lowercase letters (all letters when
1089 'ignorecase' is used)
1090*[:print:]* [:print:] printable characters including space
1091*[:punct:]* [:punct:] punctuation characters
1092*[:space:]* [:space:] whitespace characters
1093*[:upper:]* [:upper:] uppercase letters (all letters when
1094 'ignorecase' is used)
1095*[:xdigit:]* [:xdigit:] hexadecimal digits
1096*[:return:]* [:return:] the <CR> character
1097*[:tab:]* [:tab:] the <Tab> character
1098*[:escape:]* [:escape:] the <Esc> character
1099*[:backspace:]* [:backspace:] the <BS> character
1100 The brackets in character class expressions are additional to the
1101 brackets delimiting a collection. For example, the following is a
1102 plausible pattern for a UNIX filename: "[-./[:alnum:]_~]\+" That is,
1103 a list of at least one character, each of which is either '-', '.',
1104 '/', alphabetic, numeric, '_' or '~'.
Bram Moolenaarfa735342016-01-03 22:14:44 +01001105 These items only work for 8-bit characters, except [:lower:] and
1106 [:upper:] also work for multi-byte characters when using the new
Bram Moolenaar03413f42016-04-12 21:07:15 +02001107 regexp engine. See |two-engines|. In the future these items may
1108 work for multi-byte characters.
Bram Moolenaar26a60b42005-02-22 08:49:11 +00001109 */[[=* *[==]*
1110 - An equivalence class. This means that characters are matched that
Bram Moolenaar522f9ae2011-07-20 17:58:20 +02001111 have almost the same meaning, e.g., when ignoring accents. This
1112 only works for Unicode, latin1 and latin9. The form is:
Bram Moolenaarc9b4b052006-04-30 18:54:39 +00001113 [=a=]
Bram Moolenaar26a60b42005-02-22 08:49:11 +00001114 */[[.* *[..]*
1115 - A collation element. This currently simply accepts a single
1116 character in the form:
Bram Moolenaarc9b4b052006-04-30 18:54:39 +00001117 [.a.]
Bram Moolenaar071d4272004-06-13 20:20:40 +00001118 */\]*
1119 - To include a literal ']', '^', '-' or '\' in the collection, put a
1120 backslash before it: "[xyz\]]", "[\^xyz]", "[xy\-z]" and "[xyz\\]".
1121 (Note: POSIX does not support the use of a backslash this way). For
1122 ']' you can also make it the first character (following a possible
1123 "^"): "[]xyz]" or "[^]xyz]" {not in Vi}.
1124 For '-' you can also make it the first or last character: "[-xyz]",
1125 "[^-xyz]" or "[xyz-]". For '\' you can also let it be followed by
Bram Moolenaar0bc380a2010-07-10 13:52:13 +02001126 any character that's not in "^]-\bdertnoUux". "[\xyz]" matches '\',
1127 'x', 'y' and 'z'. It's better to use "\\" though, future expansions
1128 may use other characters after '\'.
Bram Moolenaarff034192013-04-24 18:51:19 +02001129 - Omitting the trailing ] is not considered an error. "[]" works like
1130 "[]]", it matches the ']' character.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001131 - The following translations are accepted when the 'l' flag is not
1132 included in 'cpoptions' {not in Vi}:
1133 \e <Esc>
1134 \t <Tab>
1135 \r <CR> (NOT end-of-line!)
1136 \b <BS>
Bram Moolenaarc81e5e72007-05-05 18:24:42 +00001137 \n line break, see above |/[\n]|
Bram Moolenaarc0197e22004-09-13 20:26:32 +00001138 \d123 decimal number of character
1139 \o40 octal number of character up to 0377
1140 \x20 hexadecimal number of character up to 0xff
1141 \u20AC hex. number of multibyte character up to 0xffff
1142 \U1234 hex. number of multibyte character up to 0xffffffff
Bram Moolenaar071d4272004-06-13 20:20:40 +00001143 NOTE: The other backslash codes mentioned above do not work inside
1144 []!
1145 - Matching with a collection can be slow, because each character in
1146 the text has to be compared with each character in the collection.
1147 Use one of the other atoms above when possible. Example: "\d" is
1148 much faster than "[0-9]" and matches the same characters.
1149
1150 */\%[]* *E69* *E70* *E369*
Bram Moolenaarc0197e22004-09-13 20:26:32 +00001151\%[] A sequence of optionally matched atoms. This always matches.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001152 It matches as much of the list of atoms it contains as possible. Thus
1153 it stops at the first atom that doesn't match. For example: >
1154 /r\%[ead]
1155< matches "r", "re", "rea" or "read". The longest that matches is used.
1156 To match the Ex command "function", where "fu" is required and
1157 "nction" is optional, this would work: >
1158 /\<fu\%[nction]\>
1159< The end-of-word atom "\>" is used to avoid matching "fu" in "full".
1160 It gets more complicated when the atoms are not ordinary characters.
1161 You don't often have to use it, but it is possible. Example: >
1162 /\<r\%[[eo]ad]\>
1163< Matches the words "r", "re", "ro", "rea", "roa", "read" and "road".
Bram Moolenaarc81e5e72007-05-05 18:24:42 +00001164 There can be no \(\), \%(\) or \z(\) items inside the [] and \%[] does
1165 not nest.
Bram Moolenaar3577c6f2008-06-24 21:16:56 +00001166 To include a "[" use "[[]" and for "]" use []]", e.g.,: >
1167 /index\%[[[]0[]]]
1168< matches "index" "index[", "index[0" and "index[0]".
Bram Moolenaardb84e452010-08-15 13:50:43 +02001169 {not available when compiled without the |+syntax| feature}
Bram Moolenaar071d4272004-06-13 20:20:40 +00001170
Bram Moolenaar677ee682005-01-27 14:41:15 +00001171 */\%d* */\%x* */\%o* */\%u* */\%U* *E678*
Bram Moolenaarc0197e22004-09-13 20:26:32 +00001172
1173\%d123 Matches the character specified with a decimal number. Must be
1174 followed by a non-digit.
1175\%o40 Matches the character specified with an octal number up to 0377.
1176 Numbers below 040 must be followed by a non-octal digit or a non-digit.
1177\%x2a Matches the character specified with up to two hexadecimal characters.
1178\%u20AC Matches the character specified with up to four hexadecimal
1179 characters.
1180\%U1234abcd Matches the character specified with up to eight hexadecimal
1181 characters.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001182
1183==============================================================================
11847. Ignoring case in a pattern */ignorecase*
1185
1186If the 'ignorecase' option is on, the case of normal letters is ignored.
1187'smartcase' can be set to ignore case when the pattern contains lowercase
1188letters only.
1189 */\c* */\C*
1190When "\c" appears anywhere in the pattern, the whole pattern is handled like
1191'ignorecase' is on. The actual value of 'ignorecase' and 'smartcase' is
1192ignored. "\C" does the opposite: Force matching case for the whole pattern.
1193{only Vim supports \c and \C}
1194Note that 'ignorecase', "\c" and "\C" are not used for the character classes.
1195
1196Examples:
1197 pattern 'ignorecase' 'smartcase' matches ~
1198 foo off - foo
1199 foo on - foo Foo FOO
1200 Foo on off foo Foo FOO
1201 Foo on on Foo
1202 \cfoo - - foo Foo FOO
1203 foo\C - - foo
1204
Bram Moolenaar071d4272004-06-13 20:20:40 +00001205Technical detail: *NL-used-for-Nul*
1206<Nul> characters in the file are stored as <NL> in memory. In the display
1207they are shown as "^@". The translation is done when reading and writing
1208files. To match a <Nul> with a search pattern you can just enter CTRL-@ or
1209"CTRL-V 000". This is probably just what you expect. Internally the
1210character is replaced with a <NL> in the search pattern. What is unusual is
1211that typing CTRL-V CTRL-J also inserts a <NL>, thus also searches for a <Nul>
1212in the file. {Vi cannot handle <Nul> characters in the file at all}
1213
1214 *CR-used-for-NL*
1215When 'fileformat' is "mac", <NL> characters in the file are stored as <CR>
Bram Moolenaare37d50a2008-08-06 17:06:04 +00001216characters internally. In the text they are shown as "^J". Otherwise this
Bram Moolenaar071d4272004-06-13 20:20:40 +00001217works similar to the usage of <NL> for a <Nul>.
1218
1219When working with expression evaluation, a <NL> character in the pattern
1220matches a <NL> in the string. The use of "\n" (backslash n) to match a <NL>
1221doesn't work there, it only works to match text in the buffer.
1222
1223 *pattern-multi-byte*
1224Patterns will also work with multi-byte characters, mostly as you would
1225expect. But invalid bytes may cause trouble, a pattern with an invalid byte
1226will probably never match.
1227
1228==============================================================================
Bram Moolenaar362e1a32006-03-06 23:29:24 +000012298. Composing characters *patterns-composing*
1230
1231 */\Z*
Bram Moolenaar8df5acf2014-05-13 19:37:29 +02001232When "\Z" appears anywhere in the pattern, all composing characters are
1233ignored. Thus only the base characters need to match, the composing
1234characters may be different and the number of composing characters may differ.
1235Only relevant when 'encoding' is "utf-8".
Bram Moolenaar543b7ef2013-06-01 14:50:56 +02001236Exception: If the pattern starts with one or more composing characters, these
1237must match.
Bram Moolenaar8df5acf2014-05-13 19:37:29 +02001238 */\%C*
1239Use "\%C" to skip any composing characters. For example, the pattern "a" does
1240not match in "càt" (where the a has the composing character 0x0300), but
1241"a\%C" does. Note that this does not match "cát" (where the á is character
12420xe1, it does not have a compositing character). It does match "cat" (where
1243the a is just an a).
Bram Moolenaar362e1a32006-03-06 23:29:24 +00001244
1245When a composing character appears at the start of the pattern of after an
1246item that doesn't include the composing character, a match is found at any
1247character that includes this composing character.
1248
1249When using a dot and a composing character, this works the same as the
1250composing character by itself, except that it doesn't matter what comes before
1251this.
1252
Bram Moolenaar543b7ef2013-06-01 14:50:56 +02001253The order of composing characters does not matter. Also, the text may have
1254more composing characters than the pattern, it still matches. But all
1255composing characters in the pattern must be found in the text.
1256
1257Suppose B is a base character and x and y are composing characters:
1258 pattern text match ~
1259 Bxy Bxy yes (perfect match)
1260 Bxy Byx yes (order ignored)
1261 Bxy By no (x missing)
1262 Bxy Bx no (y missing)
Bram Moolenaar203d04d2013-06-06 21:36:40 +02001263 Bx Bx yes (perfect match)
Bram Moolenaar543b7ef2013-06-01 14:50:56 +02001264 Bx By no (x missing)
1265 Bx Bxy yes (extra y ignored)
1266 Bx Byx yes (extra y ignored)
Bram Moolenaar362e1a32006-03-06 23:29:24 +00001267
1268==============================================================================
12699. Compare with Perl patterns *perl-patterns*
Bram Moolenaar071d4272004-06-13 20:20:40 +00001270
1271Vim's regexes are most similar to Perl's, in terms of what you can do. The
1272difference between them is mostly just notation; here's a summary of where
1273they differ:
1274
1275Capability in Vimspeak in Perlspeak ~
1276----------------------------------------------------------------
1277force case insensitivity \c (?i)
1278force case sensitivity \C (?-i)
Bram Moolenaar362e1a32006-03-06 23:29:24 +00001279backref-less grouping \%(atom\) (?:atom)
Bram Moolenaar071d4272004-06-13 20:20:40 +00001280conservative quantifiers \{-n,m} *?, +?, ??, {}?
12810-width match atom\@= (?=atom)
12820-width non-match atom\@! (?!atom)
12830-width preceding match atom\@<= (?<=atom)
12840-width preceding non-match atom\@<! (?<!atom)
1285match without retry atom\@> (?>atom)
1286
1287Vim and Perl handle newline characters inside a string a bit differently:
1288
1289In Perl, ^ and $ only match at the very beginning and end of the text,
1290by default, but you can set the 'm' flag, which lets them match at
1291embedded newlines as well. You can also set the 's' flag, which causes
1292a . to match newlines as well. (Both these flags can be changed inside
1293a pattern using the same syntax used for the i flag above, BTW.)
1294
1295On the other hand, Vim's ^ and $ always match at embedded newlines, and
1296you get two separate atoms, \%^ and \%$, which only match at the very
1297start and end of the text, respectively. Vim solves the second problem
1298by giving you the \_ "modifier": put it in front of a . or a character
1299class, and they will match newlines as well.
1300
1301Finally, these constructs are unique to Perl:
1302- execution of arbitrary code in the regex: (?{perl code})
1303- conditional expressions: (?(condition)true-expr|false-expr)
1304
1305...and these are unique to Vim:
1306- changing the magic-ness of a pattern: \v \V \m \M
1307 (very useful for avoiding backslashitis)
1308- sequence of optionally matching atoms: \%[atoms]
1309- \& (which is to \| what "and" is to "or"; it forces several branches
1310 to match at one spot)
1311- matching lines/columns by number: \%5l \%5c \%5v
Bram Moolenaar362e1a32006-03-06 23:29:24 +00001312- setting the start and end of the match: \zs \ze
Bram Moolenaar071d4272004-06-13 20:20:40 +00001313
1314==============================================================================
Bram Moolenaar362e1a32006-03-06 23:29:24 +0000131510. Highlighting matches *match-highlight*
Bram Moolenaar071d4272004-06-13 20:20:40 +00001316
1317 *:mat* *:match*
1318:mat[ch] {group} /{pattern}/
1319 Define a pattern to highlight in the current window. It will
1320 be highlighted with {group}. Example: >
1321 :highlight MyGroup ctermbg=green guibg=green
1322 :match MyGroup /TODO/
1323< Instead of // any character can be used to mark the start and
1324 end of the {pattern}. Watch out for using special characters,
1325 such as '"' and '|'.
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001326
Bram Moolenaar071d4272004-06-13 20:20:40 +00001327 {group} must exist at the moment this command is executed.
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001328
1329 The {group} highlighting still applies when a character is
Bram Moolenaar6ee10162007-07-26 20:58:42 +00001330 to be highlighted for 'hlsearch', as the highlighting for
1331 matches is given higher priority than that of 'hlsearch'.
1332 Syntax highlighting (see 'syntax') is also overruled by
1333 matches.
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001334
Bram Moolenaar071d4272004-06-13 20:20:40 +00001335 Note that highlighting the last used search pattern with
1336 'hlsearch' is used in all windows, while the pattern defined
1337 with ":match" only exists in the current window. It is kept
1338 when switching to another buffer.
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001339
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001340 'ignorecase' does not apply, use |/\c| in the pattern to
1341 ignore case. Otherwise case is not ignored.
1342
Bram Moolenaar3577c6f2008-06-24 21:16:56 +00001343 'redrawtime' defines the maximum time searched for pattern
1344 matches.
1345
Bram Moolenaarc81e5e72007-05-05 18:24:42 +00001346 When matching end-of-line and Vim redraws only part of the
1347 display you may get unexpected results. That is because Vim
1348 looks for a match in the line where redrawing starts.
1349
Bram Moolenaar3577c6f2008-06-24 21:16:56 +00001350 Also see |matcharg()| and |getmatches()|. The former returns
Bram Moolenaar6ee10162007-07-26 20:58:42 +00001351 the highlight group and pattern of a previous |:match|
1352 command. The latter returns a list with highlight groups and
1353 patterns defined by both |matchadd()| and |:match|.
1354
1355 Highlighting matches using |:match| are limited to three
Bram Moolenaar822ff862014-06-12 21:46:14 +02001356 matches (aside from |:match|, |:2match| and |:3match| are
Bram Moolenaar6ee10162007-07-26 20:58:42 +00001357 available). |matchadd()| does not have this limitation and in
1358 addition makes it possible to prioritize matches.
Bram Moolenaar910f66f2006-04-05 20:41:53 +00001359
Bram Moolenaar071d4272004-06-13 20:20:40 +00001360 Another example, which highlights all characters in virtual
1361 column 72 and more: >
1362 :highlight rightMargin term=bold ctermfg=blue guifg=blue
1363 :match rightMargin /.\%>72v/
1364< To highlight all character that are in virtual column 7: >
1365 :highlight col8 ctermbg=grey guibg=grey
1366 :match col8 /\%<8v.\%>7v/
1367< Note the use of two items to also match a character that
1368 occupies more than one virtual column, such as a TAB.
1369
1370:mat[ch]
1371:mat[ch] none
1372 Clear a previously defined match pattern.
1373
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001374
Bram Moolenaar910f66f2006-04-05 20:41:53 +00001375:2mat[ch] {group} /{pattern}/ *:2match*
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001376:2mat[ch]
1377:2mat[ch] none
Bram Moolenaar910f66f2006-04-05 20:41:53 +00001378:3mat[ch] {group} /{pattern}/ *:3match*
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001379:3mat[ch]
1380:3mat[ch] none
1381 Just like |:match| above, but set a separate match. Thus
1382 there can be three matches active at the same time. The match
1383 with the lowest number has priority if several match at the
1384 same position.
1385 The ":3match" command is used by the |matchparen| plugin. You
1386 are suggested to use ":match" for manual matching and
1387 ":2match" for another plugin.
1388
1389
Bram Moolenaar071d4272004-06-13 20:20:40 +00001390 vim:tw=78:ts=8:ft=help:norl: