blob: f66ac170ae9b1f886f962550d5160ac4e44aa684 [file] [log] [blame]
Bram Moolenaarfb539272014-08-22 19:21:47 +02001*pattern.txt* For Vim version 7.4. Last change: 2014 Jul 30
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.
62 |last-pattern| {Vi: no count}
63
64 *N*
65N Repeat the latest "/" or "?" [count] times in
66 opposite direction. |last-pattern| {Vi: no count}
67
68 *star* *E348* *E349*
69* Search forward for the [count]'th occurrence of the
70 word nearest to the cursor. The word used for the
71 search is the first of:
72 1. the keyword under the cursor |'iskeyword'|
73 2. the first keyword after the cursor, in the
74 current line
75 3. the non-blank word under the cursor
76 4. the first non-blank word after the cursor,
77 in the current line
78 Only whole keywords are searched for, like with the
79 command "/\<keyword\>". |exclusive| {not in Vi}
80 'ignorecase' is used, 'smartcase' is not.
81
82 *#*
83# Same as "*", but search backward. The pound sign
84 (character 163) also works. If the "#" key works as
85 backspace, try using "stty erase <BS>" before starting
86 Vim (<BS> is CTRL-H or a real backspace). {not in Vi}
87
88 *gstar*
89g* Like "*", but don't put "\<" and "\>" around the word.
90 This makes the search also find matches that are not a
91 whole word. {not in Vi}
92
93 *g#*
94g# Like "#", but don't put "\<" and "\>" around the word.
95 This makes the search also find matches that are not a
96 whole word. {not in Vi}
97
98 *gd*
99gd Goto local Declaration. When the cursor is on a local
100 variable, this command will jump to its declaration.
101 First Vim searches for the start of the current
102 function, just like "[[". If it is not found the
103 search stops in line 1. If it is found, Vim goes back
104 until a blank line is found. From this position Vim
105 searches for the keyword under the cursor, like with
106 "*", but lines that look like a comment are ignored
107 (see 'comments' option).
108 Note that this is not guaranteed to work, Vim does not
109 really check the syntax, it only searches for a match
110 with the keyword. If included files also need to be
111 searched use the commands listed in |include-search|.
112 After this command |n| searches forward for the next
113 match (not backward).
114 {not in Vi}
115
116 *gD*
117gD Goto global Declaration. When the cursor is on a
118 global variable that is defined in the file, this
119 command will jump to its declaration. This works just
120 like "gd", except that the search for the keyword
121 always starts in line 1. {not in Vi}
122
Bram Moolenaarf75a9632005-09-13 21:20:47 +0000123 *1gd*
1241gd Like "gd", but ignore matches inside a {} block that
125 ends before the cursor position. {not in Vi}
126
127 *1gD*
1281gD Like "gD", but ignore matches inside a {} block that
129 ends before the cursor position. {not in Vi}
130
Bram Moolenaar071d4272004-06-13 20:20:40 +0000131 *CTRL-C*
132CTRL-C Interrupt current (search) command. Use CTRL-Break on
133 MS-DOS |dos-CTRL-Break|.
134 In Normal mode, any pending command is aborted.
135
136 *:noh* *:nohlsearch*
137:noh[lsearch] Stop the highlighting for the 'hlsearch' option. It
138 is automatically turned back on when using a search
139 command, or setting the 'hlsearch' option.
140 This command doesn't work in an autocommand, because
141 the highlighting state is saved and restored when
142 executing autocommands |autocmd-searchpat|.
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000143 Same thing for when invoking a user function.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000144
145While typing the search pattern the current match will be shown if the
146'incsearch' option is on. Remember that you still have to finish the search
147command with <CR> to actually position the cursor at the displayed match. Or
148use <Esc> to abandon the search.
149
150All matches for the last used search pattern will be highlighted if you set
151the 'hlsearch' option. This can be suspended with the |:nohlsearch| command.
152
Bram Moolenaar15146672011-10-20 22:22:38 +0200153When no match is found you get the error: *E486* Pattern not found
154Note that for the |:global| command this behaves like a normal message, for Vi
155compatibility. For the |:s| command the "e" flag can be used to avoid the
156error message |:s_flags|.
157
Bram Moolenaar071d4272004-06-13 20:20:40 +0000158 *search-offset* *{offset}*
159These commands search for the specified pattern. With "/" and "?" an
160additional offset may be given. There are two types of offsets: line offsets
161and character offsets. {the character offsets are not in Vi}
162
163The offset gives the cursor position relative to the found match:
164 [num] [num] lines downwards, in column 1
165 +[num] [num] lines downwards, in column 1
166 -[num] [num] lines upwards, in column 1
167 e[+num] [num] characters to the right of the end of the match
168 e[-num] [num] characters to the left of the end of the match
169 s[+num] [num] characters to the right of the start of the match
170 s[-num] [num] characters to the left of the start of the match
171 b[+num] [num] identical to s[+num] above (mnemonic: begin)
172 b[-num] [num] identical to s[-num] above (mnemonic: begin)
Bram Moolenaar1d2ba7f2006-02-14 22:29:30 +0000173 ;{pattern} perform another search, see |//;|
Bram Moolenaar071d4272004-06-13 20:20:40 +0000174
175If a '-' or '+' is given but [num] is omitted, a count of one will be used.
176When including an offset with 'e', the search becomes inclusive (the
177character the cursor lands on is included in operations).
178
179Examples:
180
181pattern cursor position ~
182/test/+1 one line below "test", in column 1
183/test/e on the last t of "test"
184/test/s+2 on the 's' of "test"
185/test/b-3 three characters before "test"
186
187If one of these commands is used after an operator, the characters between
188the cursor position before and after the search is affected. However, if a
189line offset is given, the whole lines between the two cursor positions are
190affected.
191
192An example of how to search for matches with a pattern and change the match
193with another word: >
194 /foo<CR> find "foo"
Bram Moolenaar92dff182014-02-11 19:15:50 +0100195 c//e<CR> change until end of match
Bram Moolenaar071d4272004-06-13 20:20:40 +0000196 bar<Esc> type replacement
197 //<CR> go to start of next match
Bram Moolenaar92dff182014-02-11 19:15:50 +0100198 c//e<CR> change until end of match
Bram Moolenaar071d4272004-06-13 20:20:40 +0000199 beep<Esc> type another replacement
200 etc.
201<
202 *//;* *E386*
203A very special offset is ';' followed by another search command. For example: >
204
205 /test 1/;/test
206 /test.*/+1;?ing?
207
208The first one first finds the next occurrence of "test 1", and then the first
209occurrence of "test" after that.
210
211This is like executing two search commands after each other, except that:
212- It can be used as a single motion command after an operator.
213- The direction for a following "n" or "N" command comes from the first
214 search command.
215- When an error occurs the cursor is not moved at all.
216
217 *last-pattern*
218The last used pattern and offset are remembered. They can be used to repeat
219the search, possibly in another direction or with another count. Note that
220two patterns are remembered: One for 'normal' search commands and one for the
221substitute command ":s". Each time an empty pattern is given, the previously
Bram Moolenaar662db672011-03-22 14:05:35 +0100222used pattern is used. However, if there is no previous search command, a
223previous substitute pattern is used, if possible.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000224
225The 'magic' option sticks with the last used pattern. If you change 'magic',
226this will not change how the last used pattern will be interpreted.
227The 'ignorecase' option does not do this. When 'ignorecase' is changed, it
228will result in the pattern to match other text.
229
230All matches for the last used search pattern will be highlighted if you set
231the 'hlsearch' option.
232
233To clear the last used search pattern: >
234 :let @/ = ""
235This will not set the pattern to an empty string, because that would match
236everywhere. The pattern is really cleared, like when starting Vim.
237
Bram Moolenaar8f999f12005-01-25 22:12:55 +0000238The search usually skips matches that don't move the cursor. Whether the next
Bram Moolenaar071d4272004-06-13 20:20:40 +0000239match is found at the next character or after the skipped match depends on the
240'c' flag in 'cpoptions'. See |cpo-c|.
241 with 'c' flag: "/..." advances 1 to 3 characters
242 without 'c' flag: "/..." advances 1 character
243The unpredictability with the 'c' flag is caused by starting the search in the
244first column, skipping matches until one is found past the cursor position.
245
Bram Moolenaar8f999f12005-01-25 22:12:55 +0000246When searching backwards, searching starts at the start of the line, using the
247'c' flag in 'cpoptions' as described above. Then the last match before the
248cursor position is used.
249
Bram Moolenaar071d4272004-06-13 20:20:40 +0000250In Vi the ":tag" command sets the last search pattern when the tag is searched
251for. In Vim this is not done, the previous search pattern is still remembered,
252unless the 't' flag is present in 'cpoptions'. The search pattern is always
253put in the search history.
254
255If the 'wrapscan' option is on (which is the default), searches wrap around
256the end of the buffer. If 'wrapscan' is not set, the backward search stops
257at the beginning and the forward search stops at the end of the buffer. If
258'wrapscan' is set and the pattern was not found the error message "pattern
259not found" is given, and the cursor will not be moved. If 'wrapscan' is not
260set the message becomes "search hit BOTTOM without match" when searching
261forward, or "search hit TOP without match" when searching backward. If
262wrapscan is set and the search wraps around the end of the file the message
263"search hit TOP, continuing at BOTTOM" or "search hit BOTTOM, continuing at
264TOP" is given when searching backwards or forwards respectively. This can be
265switched off by setting the 's' flag in the 'shortmess' option. The highlight
266method 'w' is used for this message (default: standout).
267
268 *search-range*
Bram Moolenaar4770d092006-01-12 23:22:24 +0000269You can limit the search command "/" to a certain range of lines by including
270\%>l items. For example, to match the word "limit" below line 199 and above
271line 300: >
272 /\%>199l\%<300llimit
273Also see |/\%>l|.
274
275Another way is to use the ":substitute" command with the 'c' flag. Example: >
Bram Moolenaar071d4272004-06-13 20:20:40 +0000276 :.,300s/Pattern//gc
277This command will search from the cursor position until line 300 for
278"Pattern". At the match, you will be asked to type a character. Type 'q' to
279stop at this match, type 'n' to find the next match.
280
281The "*", "#", "g*" and "g#" commands look for a word near the cursor in this
282order, the first one that is found is used:
283- The keyword currently under the cursor.
284- The first keyword to the right of the cursor, in the same line.
285- The WORD currently under the cursor.
286- The first WORD to the right of the cursor, in the same line.
287The keyword may only contain letters and characters in 'iskeyword'.
288The WORD may contain any non-blanks (<Tab>s and/or <Space>s).
289Note that if you type with ten fingers, the characters are easy to remember:
290the "#" is under your left hand middle finger (search to the left and up) and
291the "*" is under your right hand middle finger (search to the right and down).
292(this depends on your keyboard layout though).
293
294==============================================================================
2952. The definition of a pattern *search-pattern* *pattern* *[pattern]*
296 *regular-expression* *regexp* *Pattern*
Bram Moolenaarf1f8bc52005-03-07 23:20:08 +0000297 *E76* *E383* *E476*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000298
299For starters, read chapter 27 of the user manual |usr_27.txt|.
300
301 */bar* */\bar* */pattern*
3021. A pattern is one or more branches, separated by "\|". It matches anything
303 that matches one of the branches. Example: "foo\|beep" matches "foo" and
304 matches "beep". If more than one branch matches, the first one is used.
305
306 pattern ::= branch
307 or branch \| branch
308 or branch \| branch \| branch
309 etc.
310
311 */branch* */\&*
3122. A branch is one or more concats, separated by "\&". It matches the last
313 concat, but only if all the preceding concats also match at the same
314 position. Examples:
315 "foobeep\&..." matches "foo" in "foobeep".
316 ".*Peter\&.*Bob" matches in a line containing both "Peter" and "Bob"
317
318 branch ::= concat
319 or concat \& concat
320 or concat \& concat \& concat
321 etc.
322
323 */concat*
3243. A concat is one or more pieces, concatenated. It matches a match for the
325 first piece, followed by a match for the second piece, etc. Example:
326 "f[0-9]b", first matches "f", then a digit and then "b".
327
328 concat ::= piece
329 or piece piece
330 or piece piece piece
331 etc.
332
333 */piece*
3344. A piece is an atom, possibly followed by a multi, an indication of how many
335 times the atom can be matched. Example: "a*" matches any sequence of "a"
336 characters: "", "a", "aa", etc. See |/multi|.
337
338 piece ::= atom
339 or atom multi
340
341 */atom*
3425. An atom can be one of a long list of items. Many atoms match one character
343 in the text. It is often an ordinary character or a character class.
344 Braces can be used to make a pattern into an atom. The "\z(\)" construct
345 is only for syntax highlighting.
346
347 atom ::= ordinary-atom |/ordinary-atom|
348 or \( pattern \) |/\(|
349 or \%( pattern \) |/\%(|
350 or \z( pattern \) |/\z(|
351
352
Bram Moolenaar913df812013-07-06 15:44:11 +0200353 */\%#=* *two-engines* *NFA*
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200354Vim includes two regexp engines:
3551. An old, backtracking engine that supports everything.
3562. A new, NFA engine that works much faster on some patterns, but does not
357 support everything.
358
359Vim will automatically select the right engine for you. However, if you run
360into a problem or want to specifically select one engine or the other, you can
361prepend one of the following to the pattern:
362
363 \%#=0 Force automatic selection. Only has an effect when
364 'regexpengine' has been set to a non-zero value.
365 \%#=1 Force using the old engine.
366 \%#=2 Force using the NFA engine.
367
368You can also use the 'regexpengine' option to change the default.
369
370 *E864* *E868* *E874* *E875* *E876* *E877* *E878*
371If selecting the NFA engine and it runs into something that is not implemented
372the pattern will not match. This is only useful when debugging Vim.
373
Bram Moolenaar071d4272004-06-13 20:20:40 +0000374==============================================================================
Bram Moolenaareb3593b2006-04-22 22:33:57 +00003753. Magic */magic*
376
377Some characters in the pattern are taken literally. They match with the same
378character in the text. When preceded with a backslash however, these
379characters get a special meaning.
380
381Other characters have a special meaning without a backslash. They need to be
382preceded with a backslash to match literally.
383
384If a character is taken literally or not depends on the 'magic' option and the
385items mentioned next.
386 */\m* */\M*
387Use of "\m" makes the pattern after it be interpreted as if 'magic' is set,
388ignoring the actual value of the 'magic' option.
389Use of "\M" makes the pattern after it be interpreted as if 'nomagic' is used.
390 */\v* */\V*
391Use of "\v" means that in the pattern after it all ASCII characters except
392'0'-'9', 'a'-'z', 'A'-'Z' and '_' have a special meaning. "very magic"
393
394Use of "\V" means that in the pattern after it only the backslash has a
395special meaning. "very nomagic"
396
397Examples:
398after: \v \m \M \V matches ~
399 'magic' 'nomagic'
400 $ $ $ \$ matches end-of-line
401 . . \. \. matches any character
402 * * \* \* any number of the previous atom
403 () \(\) \(\) \(\) grouping into an atom
404 | \| \| \| separating alternatives
405 \a \a \a \a alphabetic character
406 \\ \\ \\ \\ literal backslash
407 \. \. . . literal dot
408 \{ { { { literal '{'
409 a a a a literal 'a'
410
411{only Vim supports \m, \M, \v and \V}
412
413It is recommended to always keep the 'magic' option at the default setting,
414which is 'magic'. This avoids portability problems. To make a pattern immune
415to the 'magic' option being set or not, put "\m" or "\M" at the start of the
416pattern.
417
418==============================================================================
Bram Moolenaar071d4272004-06-13 20:20:40 +00004194. Overview of pattern items *pattern-overview*
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200420 *E865* *E866* *E867* *E869*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000421
422Overview of multi items. */multi* *E61* *E62*
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200423More explanation and examples below, follow the links. *E64* *E871*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000424
425 multi ~
426 'magic' 'nomagic' matches of the preceding atom ~
427|/star| * \* 0 or more as many as possible
428|/\+| \+ \+ 1 or more as many as possible (*)
429|/\=| \= \= 0 or 1 as many as possible (*)
430|/\?| \? \? 0 or 1 as many as possible (*)
431
432|/\{| \{n,m} \{n,m} n to m as many as possible (*)
433 \{n} \{n} n exactly (*)
434 \{n,} \{n,} at least n as many as possible (*)
435 \{,m} \{,m} 0 to m as many as possible (*)
436 \{} \{} 0 or more as many as possible (same as *) (*)
437
438|/\{-| \{-n,m} \{-n,m} n to m as few as possible (*)
439 \{-n} \{-n} n exactly (*)
440 \{-n,} \{-n,} at least n as few as possible (*)
441 \{-,m} \{-,m} 0 to m as few as possible (*)
442 \{-} \{-} 0 or more as few as possible (*)
443
444 *E59*
445|/\@>| \@> \@> 1, like matching a whole pattern (*)
446|/\@=| \@= \@= nothing, requires a match |/zero-width| (*)
447|/\@!| \@! \@! nothing, requires NO match |/zero-width| (*)
448|/\@<=| \@<= \@<= nothing, requires a match behind |/zero-width| (*)
449|/\@<!| \@<! \@<! nothing, requires NO match behind |/zero-width| (*)
450
451(*) {not in Vi}
452
453
454Overview of ordinary atoms. */ordinary-atom*
455More explanation and examples below, follow the links.
456
457 ordinary atom ~
458 magic nomagic matches ~
459|/^| ^ ^ start-of-line (at start of pattern) |/zero-width|
460|/\^| \^ \^ literal '^'
461|/\_^| \_^ \_^ start-of-line (used anywhere) |/zero-width|
462|/$| $ $ end-of-line (at end of pattern) |/zero-width|
463|/\$| \$ \$ literal '$'
464|/\_$| \_$ \_$ end-of-line (used anywhere) |/zero-width|
465|/.| . \. any single character (not an end-of-line)
466|/\_.| \_. \_. any single character or end-of-line
467|/\<| \< \< beginning of a word |/zero-width|
468|/\>| \> \> end of a word |/zero-width|
469|/\zs| \zs \zs anything, sets start of match
470|/\ze| \ze \ze anything, sets end of match
471|/\%^| \%^ \%^ beginning of file |/zero-width| *E71*
472|/\%$| \%$ \%$ end of file |/zero-width|
Bram Moolenaar33aec762006-01-22 23:30:12 +0000473|/\%V| \%V \%V inside Visual area |/zero-width|
Bram Moolenaar071d4272004-06-13 20:20:40 +0000474|/\%#| \%# \%# cursor position |/zero-width|
Bram Moolenaar33aec762006-01-22 23:30:12 +0000475|/\%'m| \%'m \%'m mark m position |/zero-width|
Bram Moolenaar071d4272004-06-13 20:20:40 +0000476|/\%l| \%23l \%23l in line 23 |/zero-width|
477|/\%c| \%23c \%23c in column 23 |/zero-width|
478|/\%v| \%23v \%23v in virtual column 23 |/zero-width|
479
Bram Moolenaar5eb86f92004-07-26 12:53:41 +0000480Character classes {not in Vi}: */character-classes*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000481|/\i| \i \i identifier character (see 'isident' option)
482|/\I| \I \I like "\i", but excluding digits
483|/\k| \k \k keyword character (see 'iskeyword' option)
484|/\K| \K \K like "\k", but excluding digits
485|/\f| \f \f file name character (see 'isfname' option)
486|/\F| \F \F like "\f", but excluding digits
487|/\p| \p \p printable character (see 'isprint' option)
488|/\P| \P \P like "\p", but excluding digits
489|/\s| \s \s whitespace character: <Space> and <Tab>
490|/\S| \S \S non-whitespace character; opposite of \s
491|/\d| \d \d digit: [0-9]
492|/\D| \D \D non-digit: [^0-9]
493|/\x| \x \x hex digit: [0-9A-Fa-f]
494|/\X| \X \X non-hex digit: [^0-9A-Fa-f]
495|/\o| \o \o octal digit: [0-7]
496|/\O| \O \O non-octal digit: [^0-7]
497|/\w| \w \w word character: [0-9A-Za-z_]
498|/\W| \W \W non-word character: [^0-9A-Za-z_]
499|/\h| \h \h head of word character: [A-Za-z_]
500|/\H| \H \H non-head of word character: [^A-Za-z_]
501|/\a| \a \a alphabetic character: [A-Za-z]
502|/\A| \A \A non-alphabetic character: [^A-Za-z]
503|/\l| \l \l lowercase character: [a-z]
504|/\L| \L \L non-lowercase character: [^a-z]
505|/\u| \u \u uppercase character: [A-Z]
506|/\U| \U \U non-uppercase character [^A-Z]
507|/\_| \_x \_x where x is any of the characters above: character
508 class with end-of-line included
509(end of character classes)
510
511|/\e| \e \e <Esc>
512|/\t| \t \t <Tab>
513|/\r| \r \r <CR>
514|/\b| \b \b <BS>
515|/\n| \n \n end-of-line
516|/~| ~ \~ last given substitute string
517|/\1| \1 \1 same string as matched by first \(\) {not in Vi}
518|/\2| \2 \2 Like "\1", but uses second \(\)
519 ...
520|/\9| \9 \9 Like "\1", but uses ninth \(\)
521 *E68*
522|/\z1| \z1 \z1 only for syntax highlighting, see |:syn-ext-match|
523 ...
524|/\z1| \z9 \z9 only for syntax highlighting, see |:syn-ext-match|
525
526 x x a character with no special meaning matches itself
527
528|/[]| [] \[] any character specified inside the []
Bram Moolenaar00154502013-02-13 16:15:55 +0100529|/\%[]| \%[] \%[] a sequence of optionally matched atoms
Bram Moolenaar071d4272004-06-13 20:20:40 +0000530
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000531|/\c| \c \c ignore case, do not use the 'ignorecase' option
532|/\C| \C \C match case, do not use the 'ignorecase' option
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200533|/\Z| \Z \Z ignore differences in Unicode "combining characters".
534 Useful when searching voweled Hebrew or Arabic text.
535
Bram Moolenaar071d4272004-06-13 20:20:40 +0000536|/\m| \m \m 'magic' on for the following chars in the pattern
537|/\M| \M \M 'magic' off for the following chars in the pattern
538|/\v| \v \v the following chars in the pattern are "very magic"
539|/\V| \V \V the following chars in the pattern are "very nomagic"
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200540|/\%#=| \%#=1 \%#=1 select regexp engine |/zero-width|
Bram Moolenaar071d4272004-06-13 20:20:40 +0000541
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +0100542|/\%d| \%d \%d match specified decimal character (eg \%d123)
Bram Moolenaarc0197e22004-09-13 20:26:32 +0000543|/\%x| \%x \%x match specified hex character (eg \%x2a)
544|/\%o| \%o \%o match specified octal character (eg \%o040)
545|/\%u| \%u \%u match specified multibyte character (eg \%u20ac)
546|/\%U| \%U \%U match specified large multibyte character (eg
547 \%U12345678)
Bram Moolenaar8df5acf2014-05-13 19:37:29 +0200548|/\%C| \%C \%C match any composing characters
Bram Moolenaar071d4272004-06-13 20:20:40 +0000549
550Example matches ~
551\<\I\i* or
552\<\h\w*
553\<[a-zA-Z_][a-zA-Z0-9_]*
554 An identifier (e.g., in a C program).
555
556\(\.$\|\. \) A period followed by <EOL> or a space.
557
558[.!?][])"']*\($\|[ ]\) A search pattern that finds the end of a sentence,
559 with almost the same definition as the ")" command.
560
561cat\Z Both "cat" and "càt" ("a" followed by 0x0300)
562 Does not match "càt" (character 0x00e0), even
563 though it may look the same.
564
565
566==============================================================================
Bram Moolenaar071d4272004-06-13 20:20:40 +00005675. Multi items *pattern-multi-items*
568
569An atom can be followed by an indication of how many times the atom can be
570matched and in what way. This is called a multi. See |/multi| for an
571overview.
572
Bram Moolenaar071d4272004-06-13 20:20:40 +0000573 */star* */\star* *E56*
574* (use \* when 'magic' is not set)
575 Matches 0 or more of the preceding atom, as many as possible.
576 Example 'nomagic' matches ~
577 a* a\* "", "a", "aa", "aaa", etc.
578 .* \.\* anything, also an empty string, no end-of-line
579 \_.* \_.\* everything up to the end of the buffer
580 \_.*END \_.\*END everything up to and including the last "END"
581 in the buffer
582
583 Exception: When "*" is used at the start of the pattern or just after
584 "^" it matches the star character.
585
586 Be aware that repeating "\_." can match a lot of text and take a long
587 time. For example, "\_.*END" matches all text from the current
588 position to the last occurrence of "END" in the file. Since the "*"
589 will match as many as possible, this first skips over all lines until
590 the end of the file and then tries matching "END", backing up one
591 character at a time.
592
593 */\+* *E57*
594\+ Matches 1 or more of the preceding atom, as many as possible. {not in
595 Vi}
596 Example matches ~
597 ^.\+$ any non-empty line
598 \s\+ white space of at least one character
599
600 */\=*
601\= Matches 0 or 1 of the preceding atom, as many as possible. {not in Vi}
602 Example matches ~
603 foo\= "fo" and "foo"
604
605 */\?*
606\? Just like \=. Cannot be used when searching backwards with the "?"
607 command. {not in Vi}
608
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +0200609 */\{* *E58* *E60* *E554* *E870*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000610\{n,m} Matches n to m of the preceding atom, as many as possible
611\{n} Matches n of the preceding atom
612\{n,} Matches at least n of the preceding atom, as many as possible
613\{,m} Matches 0 to m of the preceding atom, as many as possible
614\{} Matches 0 or more of the preceding atom, as many as possible (like *)
615 */\{-*
616\{-n,m} matches n to m of the preceding atom, as few as possible
617\{-n} matches n of the preceding atom
618\{-n,} matches at least n of the preceding atom, as few as possible
619\{-,m} matches 0 to m of the preceding atom, as few as possible
620\{-} matches 0 or more of the preceding atom, as few as possible
621 {Vi does not have any of these}
622
Bram Moolenaar26a60b42005-02-22 08:49:11 +0000623 n and m are positive decimal numbers or zero
Bram Moolenaarc81e5e72007-05-05 18:24:42 +0000624 *non-greedy*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000625 If a "-" appears immediately after the "{", then a shortest match
626 first algorithm is used (see example below). In particular, "\{-}" is
627 the same as "*" but uses the shortest match first algorithm. BUT: A
628 match that starts earlier is preferred over a shorter match: "a\{-}b"
629 matches "aaab" in "xaaab".
630
631 Example matches ~
632 ab\{2,3}c "abbc" or "abbbc"
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000633 a\{5} "aaaaa"
634 ab\{2,}c "abbc", "abbbc", "abbbbc", etc.
635 ab\{,3}c "ac", "abc", "abbc" or "abbbc"
Bram Moolenaar071d4272004-06-13 20:20:40 +0000636 a[bc]\{3}d "abbbd", "abbcd", "acbcd", "acccd", etc.
637 a\(bc\)\{1,2}d "abcd" or "abcbcd"
638 a[bc]\{-}[cd] "abc" in "abcd"
639 a[bc]*[cd] "abcd" in "abcd"
640
641 The } may optionally be preceded with a backslash: \{n,m\}.
642
643 */\@=*
644\@= Matches the preceding atom with zero width. {not in Vi}
645 Like "(?=pattern)" in Perl.
646 Example matches ~
647 foo\(bar\)\@= "foo" in "foobar"
648 foo\(bar\)\@=foo nothing
649 */zero-width*
650 When using "\@=" (or "^", "$", "\<", "\>") no characters are included
651 in the match. These items are only used to check if a match can be
652 made. This can be tricky, because a match with following items will
653 be done in the same position. The last example above will not match
654 "foobarfoo", because it tries match "foo" in the same position where
655 "bar" matched.
656
657 Note that using "\&" works the same as using "\@=": "foo\&.." is the
658 same as "\(foo\)\@=..". But using "\&" is easier, you don't need the
659 braces.
660
661
662 */\@!*
663\@! Matches with zero width if the preceding atom does NOT match at the
664 current position. |/zero-width| {not in Vi}
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200665 Like "(?!pattern)" in Perl.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000666 Example matches ~
667 foo\(bar\)\@! any "foo" not followed by "bar"
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200668 a.\{-}p\@! "a", "ap", "app", "appp", etc. not immediately
Bram Moolenaar251e1912011-06-19 05:09:16 +0200669 followed by a "p"
Bram Moolenaar071d4272004-06-13 20:20:40 +0000670 if \(\(then\)\@!.\)*$ "if " not followed by "then"
671
672 Using "\@!" is tricky, because there are many places where a pattern
673 does not match. "a.*p\@!" will match from an "a" to the end of the
674 line, because ".*" can match all characters in the line and the "p"
675 doesn't match at the end of the line. "a.\{-}p\@!" will match any
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200676 "a", "ap", "app", etc. that isn't followed by a "p", because the "."
Bram Moolenaar071d4272004-06-13 20:20:40 +0000677 can match a "p" and "p\@!" doesn't match after that.
678
679 You can't use "\@!" to look for a non-match before the matching
680 position: "\(foo\)\@!bar" will match "bar" in "foobar", because at the
681 position where "bar" matches, "foo" does not match. To avoid matching
682 "foobar" you could use "\(foo\)\@!...bar", but that doesn't match a
Bram Moolenaar13fcaaf2005-04-15 21:13:42 +0000683 bar at the start of a line. Use "\(foo\)\@<!bar".
Bram Moolenaar071d4272004-06-13 20:20:40 +0000684
Bram Moolenaar8e5af3e2011-04-28 19:02:44 +0200685 Useful example: to find "foo" in a line that does not contain "bar": >
686 /^\%(.*bar\)\@!.*\zsfoo
687< This pattern first checks that there is not a single position in the
688 line where "bar" matches. If ".*bar" matches somewhere the \@! will
689 reject the pattern. When there is no match any "foo" will be found.
690 The "\zs" is to have the match start just before "foo".
691
Bram Moolenaar071d4272004-06-13 20:20:40 +0000692 */\@<=*
693\@<= Matches with zero width if the preceding atom matches just before what
694 follows. |/zero-width| {not in Vi}
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200695 Like "(?<=pattern)" in Perl, but Vim allows non-fixed-width patterns.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000696 Example matches ~
697 \(an\_s\+\)\@<=file "file" after "an" and white space or an
698 end-of-line
699 For speed it's often much better to avoid this multi. Try using "\zs"
700 instead |/\zs|. To match the same as the above example:
701 an\_s\+\zsfile
Bram Moolenaar543b7ef2013-06-01 14:50:56 +0200702 At least set a limit for the look-behind, see below.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000703
704 "\@<=" and "\@<!" check for matches just before what follows.
705 Theoretically these matches could start anywhere before this position.
706 But to limit the time needed, only the line where what follows matches
707 is searched, and one line before that (if there is one). This should
708 be sufficient to match most things and not be too slow.
Bram Moolenaarfb539272014-08-22 19:21:47 +0200709
710 In the old regexp engine the part of the pattern after "\@<=" and
711 "\@<!" are checked for a match first, thus things like "\1" don't work
712 to reference \(\) inside the preceding atom. It does work the other
713 way around:
714 Bad example matches ~
715 \%#=1\1\@<=,\([a-z]\+\) ",abc" in "abc,abc"
716
717 However, the new regexp engine works differently, it is better to not
718 rely on this behavior, do not use \@<= if it can be avoided:
719 Example matches ~
720 \([a-z]\+\)\zs,\1 ",abc" in "abc,abc"
Bram Moolenaar071d4272004-06-13 20:20:40 +0000721
Bram Moolenaar543b7ef2013-06-01 14:50:56 +0200722\@123<=
723 Like "\@<=" but only look back 123 bytes. This avoids trying lots
724 of matches that are known to fail and make executing the pattern very
725 slow. Example, check if there is a "<" just before "span":
726 /<\@1<=span
727 This will try matching "<" only one byte before "span", which is the
728 only place that works anyway.
729 After crossing a line boundary, the limit is relative to the end of
730 the line. Thus the characters at the start of the line with the match
731 are not counted (this is just to keep it simple).
732 The number zero is the same as no limit.
733
Bram Moolenaar071d4272004-06-13 20:20:40 +0000734 */\@<!*
735\@<! Matches with zero width if the preceding atom does NOT match just
736 before what follows. Thus this matches if there is no position in the
737 current or previous line where the atom matches such that it ends just
738 before what follows. |/zero-width| {not in Vi}
Bram Moolenaar1aeaf8c2012-05-18 13:46:39 +0200739 Like "(?<!pattern)" in Perl, but Vim allows non-fixed-width patterns.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000740 The match with the preceding atom is made to end just before the match
741 with what follows, thus an atom that ends in ".*" will work.
742 Warning: This can be slow (because many positions need to be checked
Bram Moolenaar543b7ef2013-06-01 14:50:56 +0200743 for a match). Use a limit if you can, see below.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000744 Example matches ~
745 \(foo\)\@<!bar any "bar" that's not in "foobar"
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000746 \(\/\/.*\)\@<!in "in" which is not after "//"
Bram Moolenaar071d4272004-06-13 20:20:40 +0000747
Bram Moolenaar543b7ef2013-06-01 14:50:56 +0200748\@123<!
749 Like "\@<!" but only look back 123 bytes. This avoids trying lots of
750 matches that are known to fail and make executing the pattern very
751 slow.
752
Bram Moolenaar071d4272004-06-13 20:20:40 +0000753 */\@>*
754\@> Matches the preceding atom like matching a whole pattern. {not in Vi}
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000755 Like "(?>pattern)" in Perl.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000756 Example matches ~
757 \(a*\)\@>a nothing (the "a*" takes all the "a"'s, there can't be
758 another one following)
759
760 This matches the preceding atom as if it was a pattern by itself. If
761 it doesn't match, there is no retry with shorter sub-matches or
762 anything. Observe this difference: "a*b" and "a*ab" both match
763 "aaab", but in the second case the "a*" matches only the first two
764 "a"s. "\(a*\)\@>ab" will not match "aaab", because the "a*" matches
765 the "aaa" (as many "a"s as possible), thus the "ab" can't match.
766
767
768==============================================================================
7696. Ordinary atoms *pattern-atoms*
770
771An ordinary atom can be:
772
773 */^*
774^ At beginning of pattern or after "\|", "\(", "\%(" or "\n": matches
775 start-of-line; at other positions, matches literal '^'. |/zero-width|
776 Example matches ~
777 ^beep( the start of the C function "beep" (probably).
778
779 */\^*
780\^ Matches literal '^'. Can be used at any position in the pattern.
781
782 */\_^*
783\_^ Matches start-of-line. |/zero-width| Can be used at any position in
784 the pattern.
785 Example matches ~
786 \_s*\_^foo white space and blank lines and then "foo" at
787 start-of-line
788
789 */$*
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000790$ At end of pattern or in front of "\|", "\)" or "\n" ('magic' on):
Bram Moolenaar071d4272004-06-13 20:20:40 +0000791 matches end-of-line <EOL>; at other positions, matches literal '$'.
792 |/zero-width|
793
794 */\$*
795\$ Matches literal '$'. Can be used at any position in the pattern.
796
797 */\_$*
798\_$ Matches end-of-line. |/zero-width| Can be used at any position in the
799 pattern. Note that "a\_$b" never matches, since "b" cannot match an
800 end-of-line. Use "a\nb" instead |/\n|.
801 Example matches ~
802 foo\_$\_s* "foo" at end-of-line and following white space and
803 blank lines
804
805. (with 'nomagic': \.) */.* */\.*
806 Matches any single character, but not an end-of-line.
807
808 */\_.*
809\_. Matches any single character or end-of-line.
810 Careful: "\_.*" matches all text to the end of the buffer!
811
812 */\<*
813\< Matches the beginning of a word: The next char is the first char of a
814 word. The 'iskeyword' option specifies what is a word character.
815 |/zero-width|
816
817 */\>*
818\> Matches the end of a word: The previous char is the last char of a
Bram Moolenaar13fcaaf2005-04-15 21:13:42 +0000819 word. The 'iskeyword' option specifies what is a word character.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000820 |/zero-width|
821
822 */\zs*
823\zs Matches at any position, and sets the start of the match there: The
824 next char is the first char of the whole match. |/zero-width|
825 Example: >
826 /^\s*\zsif
827< matches an "if" at the start of a line, ignoring white space.
828 Can be used multiple times, the last one encountered in a matching
Bram Moolenaar13fcaaf2005-04-15 21:13:42 +0000829 branch is used. Example: >
Bram Moolenaar071d4272004-06-13 20:20:40 +0000830 /\(.\{-}\zsFab\)\{3}
831< Finds the third occurrence of "Fab".
Bram Moolenaardb84e452010-08-15 13:50:43 +0200832 {not in Vi} {not available when compiled without the |+syntax| feature}
Bram Moolenaar071d4272004-06-13 20:20:40 +0000833 */\ze*
834\ze Matches at any position, and sets the end of the match there: The
835 previous char is the last char of the whole match. |/zero-width|
836 Can be used multiple times, the last one encountered in a matching
837 branch is used.
838 Example: "end\ze\(if\|for\)" matches the "end" in "endif" and
839 "endfor".
Bram Moolenaardb84e452010-08-15 13:50:43 +0200840 {not in Vi} {not available when compiled without the |+syntax| feature}
Bram Moolenaar071d4272004-06-13 20:20:40 +0000841
842 */\%^* *start-of-file*
843\%^ Matches start of the file. When matching with a string, matches the
844 start of the string. {not in Vi}
845 For example, to find the first "VIM" in a file: >
846 /\%^\_.\{-}\zsVIM
847<
848 */\%$* *end-of-file*
849\%$ Matches end of the file. When matching with a string, matches the
850 end of the string. {not in Vi}
851 Note that this does NOT find the last "VIM" in a file: >
852 /VIM\_.\{-}\%$
853< It will find the next VIM, because the part after it will always
854 match. This one will find the last "VIM" in the file: >
855 /VIM\ze\(\(VIM\)\@!\_.\)*\%$
856< This uses |/\@!| to ascertain that "VIM" does NOT match in any
857 position after the first "VIM".
858 Searching from the end of the file backwards is easier!
859
Bram Moolenaar33aec762006-01-22 23:30:12 +0000860 */\%V*
861\%V Match inside the Visual area. When Visual mode has already been
862 stopped match in the area that |gv| would reselect.
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +0100863 This is a |/zero-width| match. To make sure the whole pattern is
864 inside the Visual area put it at the start and end of the pattern,
865 e.g.: >
866 /\%Vfoo.*bar\%V
867< Only works for the current buffer.
Bram Moolenaar33aec762006-01-22 23:30:12 +0000868
Bram Moolenaar071d4272004-06-13 20:20:40 +0000869 */\%#* *cursor-position*
870\%# Matches with the cursor position. Only works when matching in a
871 buffer displayed in a window. {not in Vi}
872 WARNING: When the cursor is moved after the pattern was used, the
873 result becomes invalid. Vim doesn't automatically update the matches.
874 This is especially relevant for syntax highlighting and 'hlsearch'.
875 In other words: When the cursor moves the display isn't updated for
876 this change. An update is done for lines which are changed (the whole
877 line is updated) or when using the |CTRL-L| command (the whole screen
878 is updated). Example, to highlight the word under the cursor: >
879 /\k*\%#\k*
880< When 'hlsearch' is set and you move the cursor around and make changes
881 this will clearly show when the match is updated or not.
882
Bram Moolenaar33aec762006-01-22 23:30:12 +0000883 */\%'m* */\%<'m* */\%>'m*
884\%'m Matches with the position of mark m.
885\%<'m Matches before the position of mark m.
886\%>'m Matches after the position of mark m.
887 Example, to highlight the text from mark 's to 'e: >
888 /.\%>'s.*\%<'e..
889< Note that two dots are required to include mark 'e in the match. That
890 is because "\%<'e" matches at the character before the 'e mark, and
891 since it's a |/zero-width| match it doesn't include that character.
892 {not in Vi}
893 WARNING: When the mark is moved after the pattern was used, the result
894 becomes invalid. Vim doesn't automatically update the matches.
Bram Moolenaar1ef15e32006-02-01 21:56:25 +0000895 Similar to moving the cursor for "\%#" |/\%#|.
Bram Moolenaar33aec762006-01-22 23:30:12 +0000896
Bram Moolenaar071d4272004-06-13 20:20:40 +0000897 */\%l* */\%>l* */\%<l*
898\%23l Matches in a specific line.
Bram Moolenaar4770d092006-01-12 23:22:24 +0000899\%<23l Matches above a specific line (lower line number).
900\%>23l Matches below a specific line (higher line number).
Bram Moolenaar071d4272004-06-13 20:20:40 +0000901 These three can be used to match specific lines in a buffer. The "23"
902 can be any line number. The first line is 1. {not in Vi}
903 WARNING: When inserting or deleting lines Vim does not automatically
904 update the matches. This means Syntax highlighting quickly becomes
905 wrong.
906 Example, to highlight the line where the cursor currently is: >
907 :exe '/\%' . line(".") . 'l.*'
908< When 'hlsearch' is set and you move the cursor around and make changes
909 this will clearly show when the match is updated or not.
910
911 */\%c* */\%>c* */\%<c*
912\%23c Matches in a specific column.
913\%<23c Matches before a specific column.
914\%>23c Matches after a specific column.
915 These three can be used to match specific columns in a buffer or
916 string. The "23" can be any column number. The first column is 1.
917 Actually, the column is the byte number (thus it's not exactly right
918 for multi-byte characters). {not in Vi}
919 WARNING: When inserting or deleting text Vim does not automatically
920 update the matches. This means Syntax highlighting quickly becomes
921 wrong.
922 Example, to highlight the column where the cursor currently is: >
923 :exe '/\%' . col(".") . 'c'
924< When 'hlsearch' is set and you move the cursor around and make changes
925 this will clearly show when the match is updated or not.
926 Example for matching a single byte in column 44: >
927 /\%>43c.\%<46c
928< Note that "\%<46c" matches in column 45 when the "." matches a byte in
929 column 44.
930 */\%v* */\%>v* */\%<v*
931\%23v Matches in a specific virtual column.
932\%<23v Matches before a specific virtual column.
933\%>23v Matches after a specific virtual column.
934 These three can be used to match specific virtual columns in a buffer
935 or string. When not matching with a buffer in a window, the option
936 values of the current window are used (e.g., 'tabstop').
937 The "23" can be any column number. The first column is 1.
938 Note that some virtual column positions will never match, because they
Bram Moolenaar69c2f172007-05-12 14:57:31 +0000939 are halfway through a tab or other character that occupies more than
940 one screen character. {not in Vi}
Bram Moolenaar071d4272004-06-13 20:20:40 +0000941 WARNING: When inserting or deleting text Vim does not automatically
Bram Moolenaarde934d72005-05-22 22:09:40 +0000942 update highlighted matches. This means Syntax highlighting quickly
943 becomes wrong.
Bram Moolenaar3577c6f2008-06-24 21:16:56 +0000944 Example, to highlight all the characters after virtual column 72: >
Bram Moolenaar071d4272004-06-13 20:20:40 +0000945 /\%>72v.*
946< When 'hlsearch' is set and you move the cursor around and make changes
947 this will clearly show when the match is updated or not.
948 To match the text up to column 17: >
949 /.*\%17v
Bram Moolenaar8f3f58f2010-01-06 20:52:26 +0100950< Column 17 is included, because that's where the "\%17v" matches,
951 even though this is a |/zero-width| match. Adding a dot to match the
952 next character has the same result: >
953 /.*\%17v.
954< This command does the same thing, but also matches when there is no
955 character in column 17: >
956 /.*\%<18v.
Bram Moolenaar071d4272004-06-13 20:20:40 +0000957<
958
959Character classes: {not in Vi}
960\i identifier character (see 'isident' option) */\i*
961\I like "\i", but excluding digits */\I*
962\k keyword character (see 'iskeyword' option) */\k*
963\K like "\k", but excluding digits */\K*
964\f file name character (see 'isfname' option) */\f*
965\F like "\f", but excluding digits */\F*
966\p printable character (see 'isprint' option) */\p*
967\P like "\p", but excluding digits */\P*
968
969NOTE: the above also work for multi-byte characters. The ones below only
970match ASCII characters, as indicated by the range.
971
972 *whitespace* *white-space*
973\s whitespace character: <Space> and <Tab> */\s*
974\S non-whitespace character; opposite of \s */\S*
975\d digit: [0-9] */\d*
976\D non-digit: [^0-9] */\D*
977\x hex digit: [0-9A-Fa-f] */\x*
978\X non-hex digit: [^0-9A-Fa-f] */\X*
979\o octal digit: [0-7] */\o*
980\O non-octal digit: [^0-7] */\O*
981\w word character: [0-9A-Za-z_] */\w*
982\W non-word character: [^0-9A-Za-z_] */\W*
983\h head of word character: [A-Za-z_] */\h*
984\H non-head of word character: [^A-Za-z_] */\H*
985\a alphabetic character: [A-Za-z] */\a*
986\A non-alphabetic character: [^A-Za-z] */\A*
987\l lowercase character: [a-z] */\l*
988\L non-lowercase character: [^a-z] */\L*
989\u uppercase character: [A-Z] */\u*
Bram Moolenaarf1568ec2011-12-14 21:17:39 +0100990\U non-uppercase character: [^A-Z] */\U*
Bram Moolenaar071d4272004-06-13 20:20:40 +0000991
992 NOTE: Using the atom is faster than the [] form.
993
994 NOTE: 'ignorecase', "\c" and "\C" are not used by character classes.
995
996 */\_* *E63* */\_i* */\_I* */\_k* */\_K* */\_f* */\_F*
997 */\_p* */\_P* */\_s* */\_S* */\_d* */\_D* */\_x* */\_X*
998 */\_o* */\_O* */\_w* */\_W* */\_h* */\_H* */\_a* */\_A*
999 */\_l* */\_L* */\_u* */\_U*
1000\_x Where "x" is any of the characters above: The character class with
1001 end-of-line added
1002(end of character classes)
1003
1004\e matches <Esc> */\e*
1005\t matches <Tab> */\t*
1006\r matches <CR> */\r*
1007\b matches <BS> */\b*
1008\n matches an end-of-line */\n*
1009 When matching in a string instead of buffer text a literal newline
1010 character is matched.
1011
1012~ matches the last given substitute string */~* */\~*
1013
1014\(\) A pattern enclosed by escaped parentheses. */\(* */\(\)* */\)*
Bram Moolenaarfbc0d2e2013-05-19 19:40:29 +02001015 E.g., "\(^a\)" matches 'a' at the start of a line.
1016 *E51* *E54* *E55* *E872* *E873*
Bram Moolenaar071d4272004-06-13 20:20:40 +00001017
1018\1 Matches the same string that was matched by */\1* *E65*
1019 the first sub-expression in \( and \). {not in Vi}
1020 Example: "\([a-z]\).\1" matches "ata", "ehe", "tot", etc.
1021\2 Like "\1", but uses second sub-expression, */\2*
1022 ... */\3*
1023\9 Like "\1", but uses ninth sub-expression. */\9*
1024 Note: The numbering of groups is done based on which "\(" comes first
1025 in the pattern (going left to right), NOT based on what is matched
1026 first.
1027
1028\%(\) A pattern enclosed by escaped parentheses. */\%(\)* */\%(* *E53*
1029 Just like \(\), but without counting it as a sub-expression. This
1030 allows using more groups and it's a little bit faster.
1031 {not in Vi}
1032
1033x A single character, with no special meaning, matches itself
1034
1035 */\* */\\*
1036\x A backslash followed by a single character, with no special meaning,
1037 is reserved for future expansions
1038
1039[] (with 'nomagic': \[]) */[]* */\[]* */\_[]* */collection*
1040\_[]
Bram Moolenaar13fcaaf2005-04-15 21:13:42 +00001041 A collection. This is a sequence of characters enclosed in brackets.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001042 It matches any single character in the collection.
1043 Example matches ~
1044 [xyz] any 'x', 'y' or 'z'
1045 [a-zA-Z]$ any alphabetic character at the end of a line
1046 \c[a-z]$ same
Bram Moolenaara3e6bc92013-01-30 14:18:00 +01001047 [А-яЁё] Russian alphabet (with utf-8 and cp1251)
1048
Bram Moolenaarc81e5e72007-05-05 18:24:42 +00001049 */[\n]*
Bram Moolenaar071d4272004-06-13 20:20:40 +00001050 With "\_" prepended the collection also includes the end-of-line.
1051 The same can be done by including "\n" in the collection. The
1052 end-of-line is also matched when the collection starts with "^"! Thus
1053 "\_[^ab]" matches the end-of-line and any character but "a" and "b".
1054 This makes it Vi compatible: Without the "\_" or "\n" the collection
1055 does not match an end-of-line.
Bram Moolenaar8aff23a2005-08-19 20:40:30 +00001056 *E769*
Bram Moolenaarae5bce12005-08-15 21:41:48 +00001057 When the ']' is not there Vim will not give an error message but
Bram Moolenaar8aff23a2005-08-19 20:40:30 +00001058 assume no collection is used. Useful to search for '['. However, you
1059 do get E769 for internal searching.
Bram Moolenaarae5bce12005-08-15 21:41:48 +00001060
Bram Moolenaar071d4272004-06-13 20:20:40 +00001061 If the sequence begins with "^", it matches any single character NOT
1062 in the collection: "[^xyz]" matches anything but 'x', 'y' and 'z'.
1063 - If two characters in the sequence are separated by '-', this is
1064 shorthand for the full list of ASCII characters between them. E.g.,
Bram Moolenaar0bc380a2010-07-10 13:52:13 +02001065 "[0-9]" matches any decimal digit. Non-ASCII characters can be
1066 used, but the character values must not be more than 256 apart.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001067 - A character class expression is evaluated to the set of characters
1068 belonging to that character class. The following character classes
1069 are supported:
1070 Name Contents ~
1071*[:alnum:]* [:alnum:] letters and digits
1072*[:alpha:]* [:alpha:] letters
1073*[:blank:]* [:blank:] space and tab characters
1074*[:cntrl:]* [:cntrl:] control characters
1075*[:digit:]* [:digit:] decimal digits
1076*[:graph:]* [:graph:] printable characters excluding space
1077*[:lower:]* [:lower:] lowercase letters (all letters when
1078 'ignorecase' is used)
1079*[:print:]* [:print:] printable characters including space
1080*[:punct:]* [:punct:] punctuation characters
1081*[:space:]* [:space:] whitespace characters
1082*[:upper:]* [:upper:] uppercase letters (all letters when
1083 'ignorecase' is used)
1084*[:xdigit:]* [:xdigit:] hexadecimal digits
1085*[:return:]* [:return:] the <CR> character
1086*[:tab:]* [:tab:] the <Tab> character
1087*[:escape:]* [:escape:] the <Esc> character
1088*[:backspace:]* [:backspace:] the <BS> character
1089 The brackets in character class expressions are additional to the
1090 brackets delimiting a collection. For example, the following is a
1091 plausible pattern for a UNIX filename: "[-./[:alnum:]_~]\+" That is,
1092 a list of at least one character, each of which is either '-', '.',
1093 '/', alphabetic, numeric, '_' or '~'.
1094 These items only work for 8-bit characters.
Bram Moolenaar26a60b42005-02-22 08:49:11 +00001095 */[[=* *[==]*
1096 - An equivalence class. This means that characters are matched that
Bram Moolenaar522f9ae2011-07-20 17:58:20 +02001097 have almost the same meaning, e.g., when ignoring accents. This
1098 only works for Unicode, latin1 and latin9. The form is:
Bram Moolenaarc9b4b052006-04-30 18:54:39 +00001099 [=a=]
Bram Moolenaar26a60b42005-02-22 08:49:11 +00001100 */[[.* *[..]*
1101 - A collation element. This currently simply accepts a single
1102 character in the form:
Bram Moolenaarc9b4b052006-04-30 18:54:39 +00001103 [.a.]
Bram Moolenaar071d4272004-06-13 20:20:40 +00001104 */\]*
1105 - To include a literal ']', '^', '-' or '\' in the collection, put a
1106 backslash before it: "[xyz\]]", "[\^xyz]", "[xy\-z]" and "[xyz\\]".
1107 (Note: POSIX does not support the use of a backslash this way). For
1108 ']' you can also make it the first character (following a possible
1109 "^"): "[]xyz]" or "[^]xyz]" {not in Vi}.
1110 For '-' you can also make it the first or last character: "[-xyz]",
1111 "[^-xyz]" or "[xyz-]". For '\' you can also let it be followed by
Bram Moolenaar0bc380a2010-07-10 13:52:13 +02001112 any character that's not in "^]-\bdertnoUux". "[\xyz]" matches '\',
1113 'x', 'y' and 'z'. It's better to use "\\" though, future expansions
1114 may use other characters after '\'.
Bram Moolenaarff034192013-04-24 18:51:19 +02001115 - Omitting the trailing ] is not considered an error. "[]" works like
1116 "[]]", it matches the ']' character.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001117 - The following translations are accepted when the 'l' flag is not
1118 included in 'cpoptions' {not in Vi}:
1119 \e <Esc>
1120 \t <Tab>
1121 \r <CR> (NOT end-of-line!)
1122 \b <BS>
Bram Moolenaarc81e5e72007-05-05 18:24:42 +00001123 \n line break, see above |/[\n]|
Bram Moolenaarc0197e22004-09-13 20:26:32 +00001124 \d123 decimal number of character
1125 \o40 octal number of character up to 0377
1126 \x20 hexadecimal number of character up to 0xff
1127 \u20AC hex. number of multibyte character up to 0xffff
1128 \U1234 hex. number of multibyte character up to 0xffffffff
Bram Moolenaar071d4272004-06-13 20:20:40 +00001129 NOTE: The other backslash codes mentioned above do not work inside
1130 []!
1131 - Matching with a collection can be slow, because each character in
1132 the text has to be compared with each character in the collection.
1133 Use one of the other atoms above when possible. Example: "\d" is
1134 much faster than "[0-9]" and matches the same characters.
1135
1136 */\%[]* *E69* *E70* *E369*
Bram Moolenaarc0197e22004-09-13 20:26:32 +00001137\%[] A sequence of optionally matched atoms. This always matches.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001138 It matches as much of the list of atoms it contains as possible. Thus
1139 it stops at the first atom that doesn't match. For example: >
1140 /r\%[ead]
1141< matches "r", "re", "rea" or "read". The longest that matches is used.
1142 To match the Ex command "function", where "fu" is required and
1143 "nction" is optional, this would work: >
1144 /\<fu\%[nction]\>
1145< The end-of-word atom "\>" is used to avoid matching "fu" in "full".
1146 It gets more complicated when the atoms are not ordinary characters.
1147 You don't often have to use it, but it is possible. Example: >
1148 /\<r\%[[eo]ad]\>
1149< Matches the words "r", "re", "ro", "rea", "roa", "read" and "road".
Bram Moolenaarc81e5e72007-05-05 18:24:42 +00001150 There can be no \(\), \%(\) or \z(\) items inside the [] and \%[] does
1151 not nest.
Bram Moolenaar3577c6f2008-06-24 21:16:56 +00001152 To include a "[" use "[[]" and for "]" use []]", e.g.,: >
1153 /index\%[[[]0[]]]
1154< matches "index" "index[", "index[0" and "index[0]".
Bram Moolenaardb84e452010-08-15 13:50:43 +02001155 {not available when compiled without the |+syntax| feature}
Bram Moolenaar071d4272004-06-13 20:20:40 +00001156
Bram Moolenaar677ee682005-01-27 14:41:15 +00001157 */\%d* */\%x* */\%o* */\%u* */\%U* *E678*
Bram Moolenaarc0197e22004-09-13 20:26:32 +00001158
1159\%d123 Matches the character specified with a decimal number. Must be
1160 followed by a non-digit.
1161\%o40 Matches the character specified with an octal number up to 0377.
1162 Numbers below 040 must be followed by a non-octal digit or a non-digit.
1163\%x2a Matches the character specified with up to two hexadecimal characters.
1164\%u20AC Matches the character specified with up to four hexadecimal
1165 characters.
1166\%U1234abcd Matches the character specified with up to eight hexadecimal
1167 characters.
Bram Moolenaar071d4272004-06-13 20:20:40 +00001168
1169==============================================================================
11707. Ignoring case in a pattern */ignorecase*
1171
1172If the 'ignorecase' option is on, the case of normal letters is ignored.
1173'smartcase' can be set to ignore case when the pattern contains lowercase
1174letters only.
1175 */\c* */\C*
1176When "\c" appears anywhere in the pattern, the whole pattern is handled like
1177'ignorecase' is on. The actual value of 'ignorecase' and 'smartcase' is
1178ignored. "\C" does the opposite: Force matching case for the whole pattern.
1179{only Vim supports \c and \C}
1180Note that 'ignorecase', "\c" and "\C" are not used for the character classes.
1181
1182Examples:
1183 pattern 'ignorecase' 'smartcase' matches ~
1184 foo off - foo
1185 foo on - foo Foo FOO
1186 Foo on off foo Foo FOO
1187 Foo on on Foo
1188 \cfoo - - foo Foo FOO
1189 foo\C - - foo
1190
Bram Moolenaar071d4272004-06-13 20:20:40 +00001191Technical detail: *NL-used-for-Nul*
1192<Nul> characters in the file are stored as <NL> in memory. In the display
1193they are shown as "^@". The translation is done when reading and writing
1194files. To match a <Nul> with a search pattern you can just enter CTRL-@ or
1195"CTRL-V 000". This is probably just what you expect. Internally the
1196character is replaced with a <NL> in the search pattern. What is unusual is
1197that typing CTRL-V CTRL-J also inserts a <NL>, thus also searches for a <Nul>
1198in the file. {Vi cannot handle <Nul> characters in the file at all}
1199
1200 *CR-used-for-NL*
1201When 'fileformat' is "mac", <NL> characters in the file are stored as <CR>
Bram Moolenaare37d50a2008-08-06 17:06:04 +00001202characters internally. In the text they are shown as "^J". Otherwise this
Bram Moolenaar071d4272004-06-13 20:20:40 +00001203works similar to the usage of <NL> for a <Nul>.
1204
1205When working with expression evaluation, a <NL> character in the pattern
1206matches a <NL> in the string. The use of "\n" (backslash n) to match a <NL>
1207doesn't work there, it only works to match text in the buffer.
1208
1209 *pattern-multi-byte*
1210Patterns will also work with multi-byte characters, mostly as you would
1211expect. But invalid bytes may cause trouble, a pattern with an invalid byte
1212will probably never match.
1213
1214==============================================================================
Bram Moolenaar362e1a32006-03-06 23:29:24 +000012158. Composing characters *patterns-composing*
1216
1217 */\Z*
Bram Moolenaar8df5acf2014-05-13 19:37:29 +02001218When "\Z" appears anywhere in the pattern, all composing characters are
1219ignored. Thus only the base characters need to match, the composing
1220characters may be different and the number of composing characters may differ.
1221Only relevant when 'encoding' is "utf-8".
Bram Moolenaar543b7ef2013-06-01 14:50:56 +02001222Exception: If the pattern starts with one or more composing characters, these
1223must match.
Bram Moolenaar8df5acf2014-05-13 19:37:29 +02001224 */\%C*
1225Use "\%C" to skip any composing characters. For example, the pattern "a" does
1226not match in "càt" (where the a has the composing character 0x0300), but
1227"a\%C" does. Note that this does not match "cát" (where the á is character
12280xe1, it does not have a compositing character). It does match "cat" (where
1229the a is just an a).
Bram Moolenaar362e1a32006-03-06 23:29:24 +00001230
1231When a composing character appears at the start of the pattern of after an
1232item that doesn't include the composing character, a match is found at any
1233character that includes this composing character.
1234
1235When using a dot and a composing character, this works the same as the
1236composing character by itself, except that it doesn't matter what comes before
1237this.
1238
Bram Moolenaar543b7ef2013-06-01 14:50:56 +02001239The order of composing characters does not matter. Also, the text may have
1240more composing characters than the pattern, it still matches. But all
1241composing characters in the pattern must be found in the text.
1242
1243Suppose B is a base character and x and y are composing characters:
1244 pattern text match ~
1245 Bxy Bxy yes (perfect match)
1246 Bxy Byx yes (order ignored)
1247 Bxy By no (x missing)
1248 Bxy Bx no (y missing)
Bram Moolenaar203d04d2013-06-06 21:36:40 +02001249 Bx Bx yes (perfect match)
Bram Moolenaar543b7ef2013-06-01 14:50:56 +02001250 Bx By no (x missing)
1251 Bx Bxy yes (extra y ignored)
1252 Bx Byx yes (extra y ignored)
Bram Moolenaar362e1a32006-03-06 23:29:24 +00001253
1254==============================================================================
12559. Compare with Perl patterns *perl-patterns*
Bram Moolenaar071d4272004-06-13 20:20:40 +00001256
1257Vim's regexes are most similar to Perl's, in terms of what you can do. The
1258difference between them is mostly just notation; here's a summary of where
1259they differ:
1260
1261Capability in Vimspeak in Perlspeak ~
1262----------------------------------------------------------------
1263force case insensitivity \c (?i)
1264force case sensitivity \C (?-i)
Bram Moolenaar362e1a32006-03-06 23:29:24 +00001265backref-less grouping \%(atom\) (?:atom)
Bram Moolenaar071d4272004-06-13 20:20:40 +00001266conservative quantifiers \{-n,m} *?, +?, ??, {}?
12670-width match atom\@= (?=atom)
12680-width non-match atom\@! (?!atom)
12690-width preceding match atom\@<= (?<=atom)
12700-width preceding non-match atom\@<! (?<!atom)
1271match without retry atom\@> (?>atom)
1272
1273Vim and Perl handle newline characters inside a string a bit differently:
1274
1275In Perl, ^ and $ only match at the very beginning and end of the text,
1276by default, but you can set the 'm' flag, which lets them match at
1277embedded newlines as well. You can also set the 's' flag, which causes
1278a . to match newlines as well. (Both these flags can be changed inside
1279a pattern using the same syntax used for the i flag above, BTW.)
1280
1281On the other hand, Vim's ^ and $ always match at embedded newlines, and
1282you get two separate atoms, \%^ and \%$, which only match at the very
1283start and end of the text, respectively. Vim solves the second problem
1284by giving you the \_ "modifier": put it in front of a . or a character
1285class, and they will match newlines as well.
1286
1287Finally, these constructs are unique to Perl:
1288- execution of arbitrary code in the regex: (?{perl code})
1289- conditional expressions: (?(condition)true-expr|false-expr)
1290
1291...and these are unique to Vim:
1292- changing the magic-ness of a pattern: \v \V \m \M
1293 (very useful for avoiding backslashitis)
1294- sequence of optionally matching atoms: \%[atoms]
1295- \& (which is to \| what "and" is to "or"; it forces several branches
1296 to match at one spot)
1297- matching lines/columns by number: \%5l \%5c \%5v
Bram Moolenaar362e1a32006-03-06 23:29:24 +00001298- setting the start and end of the match: \zs \ze
Bram Moolenaar071d4272004-06-13 20:20:40 +00001299
1300==============================================================================
Bram Moolenaar362e1a32006-03-06 23:29:24 +0000130110. Highlighting matches *match-highlight*
Bram Moolenaar071d4272004-06-13 20:20:40 +00001302
1303 *:mat* *:match*
1304:mat[ch] {group} /{pattern}/
1305 Define a pattern to highlight in the current window. It will
1306 be highlighted with {group}. Example: >
1307 :highlight MyGroup ctermbg=green guibg=green
1308 :match MyGroup /TODO/
1309< Instead of // any character can be used to mark the start and
1310 end of the {pattern}. Watch out for using special characters,
1311 such as '"' and '|'.
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001312
Bram Moolenaar071d4272004-06-13 20:20:40 +00001313 {group} must exist at the moment this command is executed.
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001314
1315 The {group} highlighting still applies when a character is
Bram Moolenaar6ee10162007-07-26 20:58:42 +00001316 to be highlighted for 'hlsearch', as the highlighting for
1317 matches is given higher priority than that of 'hlsearch'.
1318 Syntax highlighting (see 'syntax') is also overruled by
1319 matches.
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001320
Bram Moolenaar071d4272004-06-13 20:20:40 +00001321 Note that highlighting the last used search pattern with
1322 'hlsearch' is used in all windows, while the pattern defined
1323 with ":match" only exists in the current window. It is kept
1324 when switching to another buffer.
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001325
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001326 'ignorecase' does not apply, use |/\c| in the pattern to
1327 ignore case. Otherwise case is not ignored.
1328
Bram Moolenaar3577c6f2008-06-24 21:16:56 +00001329 'redrawtime' defines the maximum time searched for pattern
1330 matches.
1331
Bram Moolenaarc81e5e72007-05-05 18:24:42 +00001332 When matching end-of-line and Vim redraws only part of the
1333 display you may get unexpected results. That is because Vim
1334 looks for a match in the line where redrawing starts.
1335
Bram Moolenaar3577c6f2008-06-24 21:16:56 +00001336 Also see |matcharg()| and |getmatches()|. The former returns
Bram Moolenaar6ee10162007-07-26 20:58:42 +00001337 the highlight group and pattern of a previous |:match|
1338 command. The latter returns a list with highlight groups and
1339 patterns defined by both |matchadd()| and |:match|.
1340
1341 Highlighting matches using |:match| are limited to three
Bram Moolenaar822ff862014-06-12 21:46:14 +02001342 matches (aside from |:match|, |:2match| and |:3match| are
Bram Moolenaar6ee10162007-07-26 20:58:42 +00001343 available). |matchadd()| does not have this limitation and in
1344 addition makes it possible to prioritize matches.
Bram Moolenaar910f66f2006-04-05 20:41:53 +00001345
Bram Moolenaar071d4272004-06-13 20:20:40 +00001346 Another example, which highlights all characters in virtual
1347 column 72 and more: >
1348 :highlight rightMargin term=bold ctermfg=blue guifg=blue
1349 :match rightMargin /.\%>72v/
1350< To highlight all character that are in virtual column 7: >
1351 :highlight col8 ctermbg=grey guibg=grey
1352 :match col8 /\%<8v.\%>7v/
1353< Note the use of two items to also match a character that
1354 occupies more than one virtual column, such as a TAB.
1355
1356:mat[ch]
1357:mat[ch] none
1358 Clear a previously defined match pattern.
1359
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001360
Bram Moolenaar910f66f2006-04-05 20:41:53 +00001361:2mat[ch] {group} /{pattern}/ *:2match*
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001362:2mat[ch]
1363:2mat[ch] none
Bram Moolenaar910f66f2006-04-05 20:41:53 +00001364:3mat[ch] {group} /{pattern}/ *:3match*
Bram Moolenaarfd2ac762006-03-01 22:09:21 +00001365:3mat[ch]
1366:3mat[ch] none
1367 Just like |:match| above, but set a separate match. Thus
1368 there can be three matches active at the same time. The match
1369 with the lowest number has priority if several match at the
1370 same position.
1371 The ":3match" command is used by the |matchparen| plugin. You
1372 are suggested to use ":match" for manual matching and
1373 ":2match" for another plugin.
1374
1375
Bram Moolenaar071d4272004-06-13 20:20:40 +00001376 vim:tw=78:ts=8:ft=help:norl: