Bram Moolenaar | 33aec76 | 2006-01-22 23:30:12 +0000 | [diff] [blame] | 1 | *pattern.txt* For Vim version 7.0aa. Last change: 2006 Jan 22 |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 2 | |
| 3 | |
| 4 | VIM REFERENCE MANUAL by Bram Moolenaar |
| 5 | |
| 6 | |
| 7 | Patterns and search commands *pattern-searches* |
| 8 | |
| 9 | The very basics can be found in section |03.9| of the user manual. A few more |
| 10 | explanations are in chapter 27 |usr_27.txt|. |
| 11 | |
| 12 | 1. Search commands |search-commands| |
| 13 | 2. The definition of a pattern |search-pattern| |
| 14 | 3. Magic |/magic| |
| 15 | 4. Overview of pattern items |pattern-overview| |
| 16 | 5. Multi items |pattern-multi-items| |
| 17 | 6. Ordinary atoms |pattern-atoms| |
| 18 | 7. Ignoring case in a pattern |/ignorecase| |
| 19 | 8. Compare with Perl patterns |perl-patterns| |
| 20 | 9. Highlighting matches |match-highlight| |
| 21 | |
| 22 | ============================================================================== |
| 23 | 1. Search commands *search-commands* *E486* |
| 24 | |
| 25 | */* |
| 26 | /{pattern}[/]<CR> Search forward for the [count]'th occurrence of |
| 27 | {pattern} |exclusive|. |
| 28 | |
| 29 | /{pattern}/{offset}<CR> Search forward for the [count]'th occurrence of |
| 30 | {pattern} and go |{offset}| lines up or down. |
| 31 | |linewise|. |
| 32 | |
| 33 | */<CR>* |
| 34 | /<CR> Search forward for the [count]'th latest used |
| 35 | pattern |last-pattern| with latest used |{offset}|. |
| 36 | |
| 37 | //{offset}<CR> Search forward for the [count]'th latest used |
| 38 | pattern |last-pattern| with new |{offset}|. If |
| 39 | {offset} is empty no offset is used. |
| 40 | |
| 41 | *?* |
| 42 | ?{pattern}[?]<CR> Search backward for the [count]'th previous |
| 43 | occurrence of {pattern} |exclusive|. |
| 44 | |
| 45 | ?{pattern}?{offset}<CR> Search backward for the [count]'th previous |
| 46 | occurrence of {pattern} and go |{offset}| lines up or |
| 47 | down |linewise|. |
| 48 | |
| 49 | *?<CR>* |
| 50 | ?<CR> Search backward for the [count]'th latest used |
| 51 | pattern |last-pattern| with latest used |{offset}|. |
| 52 | |
| 53 | ??{offset}<CR> Search backward for the [count]'th latest used |
| 54 | pattern |last-pattern| with new |{offset}|. If |
| 55 | {offset} is empty no offset is used. |
| 56 | |
| 57 | *n* |
| 58 | n Repeat the latest "/" or "?" [count] times. |
| 59 | |last-pattern| {Vi: no count} |
| 60 | |
| 61 | *N* |
| 62 | N Repeat the latest "/" or "?" [count] times in |
| 63 | opposite direction. |last-pattern| {Vi: no count} |
| 64 | |
| 65 | *star* *E348* *E349* |
| 66 | * Search forward for the [count]'th occurrence of the |
| 67 | word nearest to the cursor. The word used for the |
| 68 | search is the first of: |
| 69 | 1. the keyword under the cursor |'iskeyword'| |
| 70 | 2. the first keyword after the cursor, in the |
| 71 | current line |
| 72 | 3. the non-blank word under the cursor |
| 73 | 4. the first non-blank word after the cursor, |
| 74 | in the current line |
| 75 | Only whole keywords are searched for, like with the |
| 76 | command "/\<keyword\>". |exclusive| {not in Vi} |
| 77 | 'ignorecase' is used, 'smartcase' is not. |
| 78 | |
| 79 | *#* |
| 80 | # Same as "*", but search backward. The pound sign |
| 81 | (character 163) also works. If the "#" key works as |
| 82 | backspace, try using "stty erase <BS>" before starting |
| 83 | Vim (<BS> is CTRL-H or a real backspace). {not in Vi} |
| 84 | |
| 85 | *gstar* |
| 86 | g* Like "*", but don't put "\<" and "\>" around the word. |
| 87 | This makes the search also find matches that are not a |
| 88 | whole word. {not in Vi} |
| 89 | |
| 90 | *g#* |
| 91 | g# 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 | *gd* |
| 96 | gd Goto local Declaration. When the cursor is on a local |
| 97 | variable, this command will jump to its declaration. |
| 98 | First Vim searches for the start of the current |
| 99 | function, just like "[[". If it is not found the |
| 100 | search stops in line 1. If it is found, Vim goes back |
| 101 | until a blank line is found. From this position Vim |
| 102 | searches for the keyword under the cursor, like with |
| 103 | "*", but lines that look like a comment are ignored |
| 104 | (see 'comments' option). |
| 105 | Note that this is not guaranteed to work, Vim does not |
| 106 | really check the syntax, it only searches for a match |
| 107 | with the keyword. If included files also need to be |
| 108 | searched use the commands listed in |include-search|. |
| 109 | After this command |n| searches forward for the next |
| 110 | match (not backward). |
| 111 | {not in Vi} |
| 112 | |
| 113 | *gD* |
| 114 | gD Goto global Declaration. When the cursor is on a |
| 115 | global variable that is defined in the file, this |
| 116 | command will jump to its declaration. This works just |
| 117 | like "gd", except that the search for the keyword |
| 118 | always starts in line 1. {not in Vi} |
| 119 | |
Bram Moolenaar | f75a963 | 2005-09-13 21:20:47 +0000 | [diff] [blame] | 120 | *1gd* |
| 121 | 1gd Like "gd", but ignore matches inside a {} block that |
| 122 | ends before the cursor position. {not in Vi} |
| 123 | |
| 124 | *1gD* |
| 125 | 1gD Like "gD", but ignore matches inside a {} block that |
| 126 | ends before the cursor position. {not in Vi} |
| 127 | |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 128 | *CTRL-C* |
| 129 | CTRL-C Interrupt current (search) command. Use CTRL-Break on |
| 130 | MS-DOS |dos-CTRL-Break|. |
| 131 | In Normal mode, any pending command is aborted. |
| 132 | |
| 133 | *:noh* *:nohlsearch* |
| 134 | :noh[lsearch] Stop the highlighting for the 'hlsearch' option. It |
| 135 | is automatically turned back on when using a search |
| 136 | command, or setting the 'hlsearch' option. |
| 137 | This command doesn't work in an autocommand, because |
| 138 | the highlighting state is saved and restored when |
| 139 | executing autocommands |autocmd-searchpat|. |
| 140 | |
| 141 | While typing the search pattern the current match will be shown if the |
| 142 | 'incsearch' option is on. Remember that you still have to finish the search |
| 143 | command with <CR> to actually position the cursor at the displayed match. Or |
| 144 | use <Esc> to abandon the search. |
| 145 | |
| 146 | All matches for the last used search pattern will be highlighted if you set |
| 147 | the 'hlsearch' option. This can be suspended with the |:nohlsearch| command. |
| 148 | |
| 149 | *search-offset* *{offset}* |
| 150 | These commands search for the specified pattern. With "/" and "?" an |
| 151 | additional offset may be given. There are two types of offsets: line offsets |
| 152 | and character offsets. {the character offsets are not in Vi} |
| 153 | |
| 154 | The offset gives the cursor position relative to the found match: |
| 155 | [num] [num] lines downwards, in column 1 |
| 156 | +[num] [num] lines downwards, in column 1 |
| 157 | -[num] [num] lines upwards, in column 1 |
| 158 | e[+num] [num] characters to the right of the end of the match |
| 159 | e[-num] [num] characters to the left of the end of the match |
| 160 | s[+num] [num] characters to the right of the start of the match |
| 161 | s[-num] [num] characters to the left of the start of the match |
| 162 | b[+num] [num] identical to s[+num] above (mnemonic: begin) |
| 163 | b[-num] [num] identical to s[-num] above (mnemonic: begin) |
Bram Moolenaar | 1cd871b | 2004-12-19 22:46:22 +0000 | [diff] [blame] | 164 | ;{pattern} perform another searcn, see |//;| |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 165 | |
| 166 | If a '-' or '+' is given but [num] is omitted, a count of one will be used. |
| 167 | When including an offset with 'e', the search becomes inclusive (the |
| 168 | character the cursor lands on is included in operations). |
| 169 | |
| 170 | Examples: |
| 171 | |
| 172 | pattern cursor position ~ |
| 173 | /test/+1 one line below "test", in column 1 |
| 174 | /test/e on the last t of "test" |
| 175 | /test/s+2 on the 's' of "test" |
| 176 | /test/b-3 three characters before "test" |
| 177 | |
| 178 | If one of these commands is used after an operator, the characters between |
| 179 | the cursor position before and after the search is affected. However, if a |
| 180 | line offset is given, the whole lines between the two cursor positions are |
| 181 | affected. |
| 182 | |
| 183 | An example of how to search for matches with a pattern and change the match |
| 184 | with another word: > |
| 185 | /foo<CR> find "foo" |
| 186 | c//e change until end of match |
| 187 | bar<Esc> type replacement |
| 188 | //<CR> go to start of next match |
| 189 | c//e change until end of match |
| 190 | beep<Esc> type another replacement |
| 191 | etc. |
| 192 | < |
| 193 | *//;* *E386* |
| 194 | A very special offset is ';' followed by another search command. For example: > |
| 195 | |
| 196 | /test 1/;/test |
| 197 | /test.*/+1;?ing? |
| 198 | |
| 199 | The first one first finds the next occurrence of "test 1", and then the first |
| 200 | occurrence of "test" after that. |
| 201 | |
| 202 | This is like executing two search commands after each other, except that: |
| 203 | - It can be used as a single motion command after an operator. |
| 204 | - The direction for a following "n" or "N" command comes from the first |
| 205 | search command. |
| 206 | - When an error occurs the cursor is not moved at all. |
| 207 | |
| 208 | *last-pattern* |
| 209 | The last used pattern and offset are remembered. They can be used to repeat |
| 210 | the search, possibly in another direction or with another count. Note that |
| 211 | two patterns are remembered: One for 'normal' search commands and one for the |
| 212 | substitute command ":s". Each time an empty pattern is given, the previously |
| 213 | used pattern is used. |
| 214 | |
| 215 | The 'magic' option sticks with the last used pattern. If you change 'magic', |
| 216 | this will not change how the last used pattern will be interpreted. |
| 217 | The 'ignorecase' option does not do this. When 'ignorecase' is changed, it |
| 218 | will result in the pattern to match other text. |
| 219 | |
| 220 | All matches for the last used search pattern will be highlighted if you set |
| 221 | the 'hlsearch' option. |
| 222 | |
| 223 | To clear the last used search pattern: > |
| 224 | :let @/ = "" |
| 225 | This will not set the pattern to an empty string, because that would match |
| 226 | everywhere. The pattern is really cleared, like when starting Vim. |
| 227 | |
Bram Moolenaar | 8f999f1 | 2005-01-25 22:12:55 +0000 | [diff] [blame] | 228 | The search usually skips matches that don't move the cursor. Whether the next |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 229 | match is found at the next character or after the skipped match depends on the |
| 230 | 'c' flag in 'cpoptions'. See |cpo-c|. |
| 231 | with 'c' flag: "/..." advances 1 to 3 characters |
| 232 | without 'c' flag: "/..." advances 1 character |
| 233 | The unpredictability with the 'c' flag is caused by starting the search in the |
| 234 | first column, skipping matches until one is found past the cursor position. |
| 235 | |
Bram Moolenaar | 8f999f1 | 2005-01-25 22:12:55 +0000 | [diff] [blame] | 236 | When searching backwards, searching starts at the start of the line, using the |
| 237 | 'c' flag in 'cpoptions' as described above. Then the last match before the |
| 238 | cursor position is used. |
| 239 | |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 240 | In Vi the ":tag" command sets the last search pattern when the tag is searched |
| 241 | for. In Vim this is not done, the previous search pattern is still remembered, |
| 242 | unless the 't' flag is present in 'cpoptions'. The search pattern is always |
| 243 | put in the search history. |
| 244 | |
| 245 | If the 'wrapscan' option is on (which is the default), searches wrap around |
| 246 | the end of the buffer. If 'wrapscan' is not set, the backward search stops |
| 247 | at the beginning and the forward search stops at the end of the buffer. If |
| 248 | 'wrapscan' is set and the pattern was not found the error message "pattern |
| 249 | not found" is given, and the cursor will not be moved. If 'wrapscan' is not |
| 250 | set the message becomes "search hit BOTTOM without match" when searching |
| 251 | forward, or "search hit TOP without match" when searching backward. If |
| 252 | wrapscan is set and the search wraps around the end of the file the message |
| 253 | "search hit TOP, continuing at BOTTOM" or "search hit BOTTOM, continuing at |
| 254 | TOP" is given when searching backwards or forwards respectively. This can be |
| 255 | switched off by setting the 's' flag in the 'shortmess' option. The highlight |
| 256 | method 'w' is used for this message (default: standout). |
| 257 | |
| 258 | *search-range* |
Bram Moolenaar | 4770d09 | 2006-01-12 23:22:24 +0000 | [diff] [blame] | 259 | You can limit the search command "/" to a certain range of lines by including |
| 260 | \%>l items. For example, to match the word "limit" below line 199 and above |
| 261 | line 300: > |
| 262 | /\%>199l\%<300llimit |
| 263 | Also see |/\%>l|. |
| 264 | |
| 265 | Another way is to use the ":substitute" command with the 'c' flag. Example: > |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 266 | :.,300s/Pattern//gc |
| 267 | This command will search from the cursor position until line 300 for |
| 268 | "Pattern". At the match, you will be asked to type a character. Type 'q' to |
| 269 | stop at this match, type 'n' to find the next match. |
| 270 | |
| 271 | The "*", "#", "g*" and "g#" commands look for a word near the cursor in this |
| 272 | order, the first one that is found is used: |
| 273 | - The keyword currently under the cursor. |
| 274 | - The first keyword to the right of the cursor, in the same line. |
| 275 | - The WORD currently under the cursor. |
| 276 | - The first WORD to the right of the cursor, in the same line. |
| 277 | The keyword may only contain letters and characters in 'iskeyword'. |
| 278 | The WORD may contain any non-blanks (<Tab>s and/or <Space>s). |
| 279 | Note that if you type with ten fingers, the characters are easy to remember: |
| 280 | the "#" is under your left hand middle finger (search to the left and up) and |
| 281 | the "*" is under your right hand middle finger (search to the right and down). |
| 282 | (this depends on your keyboard layout though). |
| 283 | |
| 284 | ============================================================================== |
| 285 | 2. The definition of a pattern *search-pattern* *pattern* *[pattern]* |
| 286 | *regular-expression* *regexp* *Pattern* |
Bram Moolenaar | f1f8bc5 | 2005-03-07 23:20:08 +0000 | [diff] [blame] | 287 | *E76* *E383* *E476* |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 288 | |
| 289 | For starters, read chapter 27 of the user manual |usr_27.txt|. |
| 290 | |
| 291 | */bar* */\bar* */pattern* |
| 292 | 1. A pattern is one or more branches, separated by "\|". It matches anything |
| 293 | that matches one of the branches. Example: "foo\|beep" matches "foo" and |
| 294 | matches "beep". If more than one branch matches, the first one is used. |
| 295 | |
| 296 | pattern ::= branch |
| 297 | or branch \| branch |
| 298 | or branch \| branch \| branch |
| 299 | etc. |
| 300 | |
| 301 | */branch* */\&* |
| 302 | 2. A branch is one or more concats, separated by "\&". It matches the last |
| 303 | concat, but only if all the preceding concats also match at the same |
| 304 | position. Examples: |
| 305 | "foobeep\&..." matches "foo" in "foobeep". |
| 306 | ".*Peter\&.*Bob" matches in a line containing both "Peter" and "Bob" |
| 307 | |
| 308 | branch ::= concat |
| 309 | or concat \& concat |
| 310 | or concat \& concat \& concat |
| 311 | etc. |
| 312 | |
| 313 | */concat* |
| 314 | 3. A concat is one or more pieces, concatenated. It matches a match for the |
| 315 | first piece, followed by a match for the second piece, etc. Example: |
| 316 | "f[0-9]b", first matches "f", then a digit and then "b". |
| 317 | |
| 318 | concat ::= piece |
| 319 | or piece piece |
| 320 | or piece piece piece |
| 321 | etc. |
| 322 | |
| 323 | */piece* |
| 324 | 4. A piece is an atom, possibly followed by a multi, an indication of how many |
| 325 | times the atom can be matched. Example: "a*" matches any sequence of "a" |
| 326 | characters: "", "a", "aa", etc. See |/multi|. |
| 327 | |
| 328 | piece ::= atom |
| 329 | or atom multi |
| 330 | |
| 331 | */atom* |
| 332 | 5. An atom can be one of a long list of items. Many atoms match one character |
| 333 | in the text. It is often an ordinary character or a character class. |
| 334 | Braces can be used to make a pattern into an atom. The "\z(\)" construct |
| 335 | is only for syntax highlighting. |
| 336 | |
| 337 | atom ::= ordinary-atom |/ordinary-atom| |
| 338 | or \( pattern \) |/\(| |
| 339 | or \%( pattern \) |/\%(| |
| 340 | or \z( pattern \) |/\z(| |
| 341 | |
| 342 | |
| 343 | ============================================================================== |
| 344 | 4. Overview of pattern items *pattern-overview* |
| 345 | |
| 346 | Overview of multi items. */multi* *E61* *E62* |
| 347 | More explanation and examples below, follow the links. *E64* |
| 348 | |
| 349 | multi ~ |
| 350 | 'magic' 'nomagic' matches of the preceding atom ~ |
| 351 | |/star| * \* 0 or more as many as possible |
| 352 | |/\+| \+ \+ 1 or more as many as possible (*) |
| 353 | |/\=| \= \= 0 or 1 as many as possible (*) |
| 354 | |/\?| \? \? 0 or 1 as many as possible (*) |
| 355 | |
| 356 | |/\{| \{n,m} \{n,m} n to m as many as possible (*) |
| 357 | \{n} \{n} n exactly (*) |
| 358 | \{n,} \{n,} at least n as many as possible (*) |
| 359 | \{,m} \{,m} 0 to m as many as possible (*) |
| 360 | \{} \{} 0 or more as many as possible (same as *) (*) |
| 361 | |
| 362 | |/\{-| \{-n,m} \{-n,m} n to m as few as possible (*) |
| 363 | \{-n} \{-n} n exactly (*) |
| 364 | \{-n,} \{-n,} at least n as few as possible (*) |
| 365 | \{-,m} \{-,m} 0 to m as few as possible (*) |
| 366 | \{-} \{-} 0 or more as few as possible (*) |
| 367 | |
| 368 | *E59* |
| 369 | |/\@>| \@> \@> 1, like matching a whole pattern (*) |
| 370 | |/\@=| \@= \@= nothing, requires a match |/zero-width| (*) |
| 371 | |/\@!| \@! \@! nothing, requires NO match |/zero-width| (*) |
| 372 | |/\@<=| \@<= \@<= nothing, requires a match behind |/zero-width| (*) |
| 373 | |/\@<!| \@<! \@<! nothing, requires NO match behind |/zero-width| (*) |
| 374 | |
| 375 | (*) {not in Vi} |
| 376 | |
| 377 | |
| 378 | Overview of ordinary atoms. */ordinary-atom* |
| 379 | More explanation and examples below, follow the links. |
| 380 | |
| 381 | ordinary atom ~ |
| 382 | magic nomagic matches ~ |
| 383 | |/^| ^ ^ start-of-line (at start of pattern) |/zero-width| |
| 384 | |/\^| \^ \^ literal '^' |
| 385 | |/\_^| \_^ \_^ start-of-line (used anywhere) |/zero-width| |
| 386 | |/$| $ $ end-of-line (at end of pattern) |/zero-width| |
| 387 | |/\$| \$ \$ literal '$' |
| 388 | |/\_$| \_$ \_$ end-of-line (used anywhere) |/zero-width| |
| 389 | |/.| . \. any single character (not an end-of-line) |
| 390 | |/\_.| \_. \_. any single character or end-of-line |
| 391 | |/\<| \< \< beginning of a word |/zero-width| |
| 392 | |/\>| \> \> end of a word |/zero-width| |
| 393 | |/\zs| \zs \zs anything, sets start of match |
| 394 | |/\ze| \ze \ze anything, sets end of match |
| 395 | |/\%^| \%^ \%^ beginning of file |/zero-width| *E71* |
| 396 | |/\%$| \%$ \%$ end of file |/zero-width| |
Bram Moolenaar | 33aec76 | 2006-01-22 23:30:12 +0000 | [diff] [blame] | 397 | |/\%V| \%V \%V inside Visual area |/zero-width| |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 398 | |/\%#| \%# \%# cursor position |/zero-width| |
Bram Moolenaar | 33aec76 | 2006-01-22 23:30:12 +0000 | [diff] [blame] | 399 | |/\%'m| \%'m \%'m mark m position |/zero-width| |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 400 | |/\%l| \%23l \%23l in line 23 |/zero-width| |
| 401 | |/\%c| \%23c \%23c in column 23 |/zero-width| |
| 402 | |/\%v| \%23v \%23v in virtual column 23 |/zero-width| |
| 403 | |
Bram Moolenaar | 5eb86f9 | 2004-07-26 12:53:41 +0000 | [diff] [blame] | 404 | Character classes {not in Vi}: */character-classes* |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 405 | |/\i| \i \i identifier character (see 'isident' option) |
| 406 | |/\I| \I \I like "\i", but excluding digits |
| 407 | |/\k| \k \k keyword character (see 'iskeyword' option) |
| 408 | |/\K| \K \K like "\k", but excluding digits |
| 409 | |/\f| \f \f file name character (see 'isfname' option) |
| 410 | |/\F| \F \F like "\f", but excluding digits |
| 411 | |/\p| \p \p printable character (see 'isprint' option) |
| 412 | |/\P| \P \P like "\p", but excluding digits |
| 413 | |/\s| \s \s whitespace character: <Space> and <Tab> |
| 414 | |/\S| \S \S non-whitespace character; opposite of \s |
| 415 | |/\d| \d \d digit: [0-9] |
| 416 | |/\D| \D \D non-digit: [^0-9] |
| 417 | |/\x| \x \x hex digit: [0-9A-Fa-f] |
| 418 | |/\X| \X \X non-hex digit: [^0-9A-Fa-f] |
| 419 | |/\o| \o \o octal digit: [0-7] |
| 420 | |/\O| \O \O non-octal digit: [^0-7] |
| 421 | |/\w| \w \w word character: [0-9A-Za-z_] |
| 422 | |/\W| \W \W non-word character: [^0-9A-Za-z_] |
| 423 | |/\h| \h \h head of word character: [A-Za-z_] |
| 424 | |/\H| \H \H non-head of word character: [^A-Za-z_] |
| 425 | |/\a| \a \a alphabetic character: [A-Za-z] |
| 426 | |/\A| \A \A non-alphabetic character: [^A-Za-z] |
| 427 | |/\l| \l \l lowercase character: [a-z] |
| 428 | |/\L| \L \L non-lowercase character: [^a-z] |
| 429 | |/\u| \u \u uppercase character: [A-Z] |
| 430 | |/\U| \U \U non-uppercase character [^A-Z] |
| 431 | |/\_| \_x \_x where x is any of the characters above: character |
| 432 | class with end-of-line included |
| 433 | (end of character classes) |
| 434 | |
| 435 | |/\e| \e \e <Esc> |
| 436 | |/\t| \t \t <Tab> |
| 437 | |/\r| \r \r <CR> |
| 438 | |/\b| \b \b <BS> |
| 439 | |/\n| \n \n end-of-line |
| 440 | |/~| ~ \~ last given substitute string |
| 441 | |/\1| \1 \1 same string as matched by first \(\) {not in Vi} |
| 442 | |/\2| \2 \2 Like "\1", but uses second \(\) |
| 443 | ... |
| 444 | |/\9| \9 \9 Like "\1", but uses ninth \(\) |
| 445 | *E68* |
| 446 | |/\z1| \z1 \z1 only for syntax highlighting, see |:syn-ext-match| |
| 447 | ... |
| 448 | |/\z1| \z9 \z9 only for syntax highlighting, see |:syn-ext-match| |
| 449 | |
| 450 | x x a character with no special meaning matches itself |
| 451 | |
| 452 | |/[]| [] \[] any character specified inside the [] |
Bram Moolenaar | c0197e2 | 2004-09-13 20:26:32 +0000 | [diff] [blame] | 453 | |/\%[]| \%[] \%[] a sequence of optionally matched atoms |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 454 | |
| 455 | |/\c| \c \c ignore case |
| 456 | |/\C| \C \C match case |
| 457 | |/\m| \m \m 'magic' on for the following chars in the pattern |
| 458 | |/\M| \M \M 'magic' off for the following chars in the pattern |
| 459 | |/\v| \v \v the following chars in the pattern are "very magic" |
| 460 | |/\V| \V \V the following chars in the pattern are "very nomagic" |
| 461 | |/\Z| \Z \Z ignore differences in Unicode "combining characters". |
| 462 | Useful when searching voweled Hebrew or Arabic text. |
| 463 | |
Bram Moolenaar | c0197e2 | 2004-09-13 20:26:32 +0000 | [diff] [blame] | 464 | |/\%d| \%d \%d match specified decimal character (eg \%d123 |
| 465 | |/\%x| \%x \%x match specified hex character (eg \%x2a) |
| 466 | |/\%o| \%o \%o match specified octal character (eg \%o040) |
| 467 | |/\%u| \%u \%u match specified multibyte character (eg \%u20ac) |
| 468 | |/\%U| \%U \%U match specified large multibyte character (eg |
| 469 | \%U12345678) |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 470 | |
| 471 | Example matches ~ |
| 472 | \<\I\i* or |
| 473 | \<\h\w* |
| 474 | \<[a-zA-Z_][a-zA-Z0-9_]* |
| 475 | An identifier (e.g., in a C program). |
| 476 | |
| 477 | \(\.$\|\. \) A period followed by <EOL> or a space. |
| 478 | |
| 479 | [.!?][])"']*\($\|[ ]\) A search pattern that finds the end of a sentence, |
| 480 | with almost the same definition as the ")" command. |
| 481 | |
| 482 | cat\Z Both "cat" and "càt" ("a" followed by 0x0300) |
| 483 | Does not match "cà t" (character 0x00e0), even |
| 484 | though it may look the same. |
| 485 | |
| 486 | |
| 487 | ============================================================================== |
| 488 | 3. Magic */magic* |
| 489 | |
| 490 | Some characters in the pattern are taken literally. They match with the same |
| 491 | character in the text. When preceded with a backslash however, these |
| 492 | characters get a special meaning. |
| 493 | |
| 494 | Other characters have a special meaning without a backslash. They need to be |
| 495 | preceded with a backslash to match literally. |
| 496 | |
| 497 | If a character is taken literally or not depends on the 'magic' option and the |
| 498 | items mentioned next. |
| 499 | */\m* */\M* |
| 500 | Use of "\m" makes the pattern after it be interpreted as if 'magic' is set, |
| 501 | ignoring the actual value of the 'magic' option. |
| 502 | Use of "\M" makes the pattern after it be interpreted as if 'nomagic' is used. |
| 503 | */\v* */\V* |
| 504 | Use of "\v" means that in the pattern after it all ASCII characters except |
| 505 | '0'-'9', 'a'-'z', 'A'-'Z' and '_' have a special meaning. "very magic" |
| 506 | |
| 507 | Use of "\V" means that in the pattern after it only the backslash has a |
| 508 | special meaning. "very nomagic" |
| 509 | |
| 510 | Examples: |
| 511 | after: \v \m \M \V matches ~ |
| 512 | 'magic' 'nomagic' |
| 513 | $ $ $ \$ matches end-of-line |
| 514 | . . \. \. matches any character |
| 515 | * * \* \* any number of the previous atom |
| 516 | () \(\) \(\) \(\) grouping into an atom |
| 517 | | \| \| \| separating alternatives |
| 518 | \a \a \a \a alphabetic character |
| 519 | \\ \\ \\ \\ literal backslash |
| 520 | \. \. . . literal dot |
| 521 | \{ { { { literal '{' |
| 522 | a a a a literal 'a' |
| 523 | |
| 524 | {only Vim supports \m, \M, \v and \V} |
| 525 | |
| 526 | It is recommended to always keep the 'magic' option at the default setting, |
| 527 | which is 'magic'. This avoids portability problems. To make a pattern immune |
| 528 | to the 'magic' option being set or not, put "\m" or "\M" at the start of the |
| 529 | pattern. |
| 530 | |
| 531 | |
| 532 | ============================================================================== |
| 533 | 5. Multi items *pattern-multi-items* |
| 534 | |
| 535 | An atom can be followed by an indication of how many times the atom can be |
| 536 | matched and in what way. This is called a multi. See |/multi| for an |
| 537 | overview. |
| 538 | |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 539 | */star* */\star* *E56* |
| 540 | * (use \* when 'magic' is not set) |
| 541 | Matches 0 or more of the preceding atom, as many as possible. |
| 542 | Example 'nomagic' matches ~ |
| 543 | a* a\* "", "a", "aa", "aaa", etc. |
| 544 | .* \.\* anything, also an empty string, no end-of-line |
| 545 | \_.* \_.\* everything up to the end of the buffer |
| 546 | \_.*END \_.\*END everything up to and including the last "END" |
| 547 | in the buffer |
| 548 | |
| 549 | Exception: When "*" is used at the start of the pattern or just after |
| 550 | "^" it matches the star character. |
| 551 | |
| 552 | Be aware that repeating "\_." can match a lot of text and take a long |
| 553 | time. For example, "\_.*END" matches all text from the current |
| 554 | position to the last occurrence of "END" in the file. Since the "*" |
| 555 | will match as many as possible, this first skips over all lines until |
| 556 | the end of the file and then tries matching "END", backing up one |
| 557 | character at a time. |
| 558 | |
| 559 | */\+* *E57* |
| 560 | \+ Matches 1 or more of the preceding atom, as many as possible. {not in |
| 561 | Vi} |
| 562 | Example matches ~ |
| 563 | ^.\+$ any non-empty line |
| 564 | \s\+ white space of at least one character |
| 565 | |
| 566 | */\=* |
| 567 | \= Matches 0 or 1 of the preceding atom, as many as possible. {not in Vi} |
| 568 | Example matches ~ |
| 569 | foo\= "fo" and "foo" |
| 570 | |
| 571 | */\?* |
| 572 | \? Just like \=. Cannot be used when searching backwards with the "?" |
| 573 | command. {not in Vi} |
| 574 | |
| 575 | */\{* *E58* *E60* *E554* |
| 576 | \{n,m} Matches n to m of the preceding atom, as many as possible |
| 577 | \{n} Matches n of the preceding atom |
| 578 | \{n,} Matches at least n of the preceding atom, as many as possible |
| 579 | \{,m} Matches 0 to m of the preceding atom, as many as possible |
| 580 | \{} Matches 0 or more of the preceding atom, as many as possible (like *) |
| 581 | */\{-* |
| 582 | \{-n,m} matches n to m of the preceding atom, as few as possible |
| 583 | \{-n} matches n of the preceding atom |
| 584 | \{-n,} matches at least n of the preceding atom, as few as possible |
| 585 | \{-,m} matches 0 to m of the preceding atom, as few as possible |
| 586 | \{-} matches 0 or more of the preceding atom, as few as possible |
| 587 | {Vi does not have any of these} |
| 588 | |
Bram Moolenaar | 26a60b4 | 2005-02-22 08:49:11 +0000 | [diff] [blame] | 589 | n and m are positive decimal numbers or zero |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 590 | |
| 591 | If a "-" appears immediately after the "{", then a shortest match |
| 592 | first algorithm is used (see example below). In particular, "\{-}" is |
| 593 | the same as "*" but uses the shortest match first algorithm. BUT: A |
| 594 | match that starts earlier is preferred over a shorter match: "a\{-}b" |
| 595 | matches "aaab" in "xaaab". |
| 596 | |
| 597 | Example matches ~ |
| 598 | ab\{2,3}c "abbc" or "abbbc" |
| 599 | a\{5} "aaaaa". |
| 600 | ab\{2,}c "abbc", "abbbc", "abbbbc", etc |
| 601 | ab\{,3}c "ac", "abc", "abbc" or "abbbc". |
| 602 | a[bc]\{3}d "abbbd", "abbcd", "acbcd", "acccd", etc. |
| 603 | a\(bc\)\{1,2}d "abcd" or "abcbcd" |
| 604 | a[bc]\{-}[cd] "abc" in "abcd" |
| 605 | a[bc]*[cd] "abcd" in "abcd" |
| 606 | |
| 607 | The } may optionally be preceded with a backslash: \{n,m\}. |
| 608 | |
| 609 | */\@=* |
| 610 | \@= Matches the preceding atom with zero width. {not in Vi} |
| 611 | Like "(?=pattern)" in Perl. |
| 612 | Example matches ~ |
| 613 | foo\(bar\)\@= "foo" in "foobar" |
| 614 | foo\(bar\)\@=foo nothing |
| 615 | */zero-width* |
| 616 | When using "\@=" (or "^", "$", "\<", "\>") no characters are included |
| 617 | in the match. These items are only used to check if a match can be |
| 618 | made. This can be tricky, because a match with following items will |
| 619 | be done in the same position. The last example above will not match |
| 620 | "foobarfoo", because it tries match "foo" in the same position where |
| 621 | "bar" matched. |
| 622 | |
| 623 | Note that using "\&" works the same as using "\@=": "foo\&.." is the |
| 624 | same as "\(foo\)\@=..". But using "\&" is easier, you don't need the |
| 625 | braces. |
| 626 | |
| 627 | |
| 628 | */\@!* |
| 629 | \@! Matches with zero width if the preceding atom does NOT match at the |
| 630 | current position. |/zero-width| {not in Vi} |
| 631 | Like '(?!pattern)" in Perl. |
| 632 | Example matches ~ |
| 633 | foo\(bar\)\@! any "foo" not followed by "bar" |
| 634 | a.\{-}p\@! "a", "ap", "app", etc. not followed by a "p" |
| 635 | if \(\(then\)\@!.\)*$ "if " not followed by "then" |
| 636 | |
| 637 | Using "\@!" is tricky, because there are many places where a pattern |
| 638 | does not match. "a.*p\@!" will match from an "a" to the end of the |
| 639 | line, because ".*" can match all characters in the line and the "p" |
| 640 | doesn't match at the end of the line. "a.\{-}p\@!" will match any |
| 641 | "a", "ap", "aap", etc. that isn't followed by a "p", because the "." |
| 642 | can match a "p" and "p\@!" doesn't match after that. |
| 643 | |
| 644 | You can't use "\@!" to look for a non-match before the matching |
| 645 | position: "\(foo\)\@!bar" will match "bar" in "foobar", because at the |
| 646 | position where "bar" matches, "foo" does not match. To avoid matching |
| 647 | "foobar" you could use "\(foo\)\@!...bar", but that doesn't match a |
Bram Moolenaar | 13fcaaf | 2005-04-15 21:13:42 +0000 | [diff] [blame] | 648 | bar at the start of a line. Use "\(foo\)\@<!bar". |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 649 | |
| 650 | */\@<=* |
| 651 | \@<= Matches with zero width if the preceding atom matches just before what |
| 652 | follows. |/zero-width| {not in Vi} |
| 653 | Like '(?<=pattern)" in Perl, but Vim allows non-fixed-width patterns. |
| 654 | Example matches ~ |
| 655 | \(an\_s\+\)\@<=file "file" after "an" and white space or an |
| 656 | end-of-line |
| 657 | For speed it's often much better to avoid this multi. Try using "\zs" |
| 658 | instead |/\zs|. To match the same as the above example: |
| 659 | an\_s\+\zsfile |
| 660 | |
| 661 | "\@<=" and "\@<!" check for matches just before what follows. |
| 662 | Theoretically these matches could start anywhere before this position. |
| 663 | But to limit the time needed, only the line where what follows matches |
| 664 | is searched, and one line before that (if there is one). This should |
| 665 | be sufficient to match most things and not be too slow. |
| 666 | The part of the pattern after "\@<=" and "\@<!" are checked for a |
| 667 | match first, thus things like "\1" don't work to reference \(\) inside |
| 668 | the preceding atom. It does work the other way around: |
| 669 | Example matches ~ |
| 670 | \1\@<=,\([a-z]\+\) ",abc" in "abc,abc" |
| 671 | |
| 672 | */\@<!* |
| 673 | \@<! Matches with zero width if the preceding atom does NOT match just |
| 674 | before what follows. Thus this matches if there is no position in the |
| 675 | current or previous line where the atom matches such that it ends just |
| 676 | before what follows. |/zero-width| {not in Vi} |
| 677 | Like '(?<!pattern)" in Perl, but Vim allows non-fixed-width patterns. |
| 678 | The match with the preceding atom is made to end just before the match |
| 679 | with what follows, thus an atom that ends in ".*" will work. |
| 680 | Warning: This can be slow (because many positions need to be checked |
| 681 | for a match). |
| 682 | Example matches ~ |
| 683 | \(foo\)\@<!bar any "bar" that's not in "foobar" |
| 684 | \(\/\/.*\)\@\<!in "in" which is not after "//" |
| 685 | |
| 686 | */\@>* |
| 687 | \@> Matches the preceding atom like matching a whole pattern. {not in Vi} |
| 688 | Like '(?>pattern)" in Perl. |
| 689 | Example matches ~ |
| 690 | \(a*\)\@>a nothing (the "a*" takes all the "a"'s, there can't be |
| 691 | another one following) |
| 692 | |
| 693 | This matches the preceding atom as if it was a pattern by itself. If |
| 694 | it doesn't match, there is no retry with shorter sub-matches or |
| 695 | anything. Observe this difference: "a*b" and "a*ab" both match |
| 696 | "aaab", but in the second case the "a*" matches only the first two |
| 697 | "a"s. "\(a*\)\@>ab" will not match "aaab", because the "a*" matches |
| 698 | the "aaa" (as many "a"s as possible), thus the "ab" can't match. |
| 699 | |
| 700 | |
| 701 | ============================================================================== |
| 702 | 6. Ordinary atoms *pattern-atoms* |
| 703 | |
| 704 | An ordinary atom can be: |
| 705 | |
| 706 | */^* |
| 707 | ^ At beginning of pattern or after "\|", "\(", "\%(" or "\n": matches |
| 708 | start-of-line; at other positions, matches literal '^'. |/zero-width| |
| 709 | Example matches ~ |
| 710 | ^beep( the start of the C function "beep" (probably). |
| 711 | |
| 712 | */\^* |
| 713 | \^ Matches literal '^'. Can be used at any position in the pattern. |
| 714 | |
| 715 | */\_^* |
| 716 | \_^ Matches start-of-line. |/zero-width| Can be used at any position in |
| 717 | the pattern. |
| 718 | Example matches ~ |
| 719 | \_s*\_^foo white space and blank lines and then "foo" at |
| 720 | start-of-line |
| 721 | |
| 722 | */$* |
| 723 | $ At end of pattern or in front of "\|" or "\)" ("|" or ")" after "\v"): |
| 724 | matches end-of-line <EOL>; at other positions, matches literal '$'. |
| 725 | |/zero-width| |
| 726 | |
| 727 | */\$* |
| 728 | \$ Matches literal '$'. Can be used at any position in the pattern. |
| 729 | |
| 730 | */\_$* |
| 731 | \_$ Matches end-of-line. |/zero-width| Can be used at any position in the |
| 732 | pattern. Note that "a\_$b" never matches, since "b" cannot match an |
| 733 | end-of-line. Use "a\nb" instead |/\n|. |
| 734 | Example matches ~ |
| 735 | foo\_$\_s* "foo" at end-of-line and following white space and |
| 736 | blank lines |
| 737 | |
| 738 | . (with 'nomagic': \.) */.* */\.* |
| 739 | Matches any single character, but not an end-of-line. |
| 740 | |
| 741 | */\_.* |
| 742 | \_. Matches any single character or end-of-line. |
| 743 | Careful: "\_.*" matches all text to the end of the buffer! |
| 744 | |
| 745 | */\<* |
| 746 | \< Matches the beginning of a word: The next char is the first char of a |
| 747 | word. The 'iskeyword' option specifies what is a word character. |
| 748 | |/zero-width| |
| 749 | |
| 750 | */\>* |
| 751 | \> Matches the end of a word: The previous char is the last char of a |
Bram Moolenaar | 13fcaaf | 2005-04-15 21:13:42 +0000 | [diff] [blame] | 752 | word. The 'iskeyword' option specifies what is a word character. |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 753 | |/zero-width| |
| 754 | |
| 755 | */\zs* |
| 756 | \zs Matches at any position, and sets the start of the match there: The |
| 757 | next char is the first char of the whole match. |/zero-width| |
| 758 | Example: > |
| 759 | /^\s*\zsif |
| 760 | < matches an "if" at the start of a line, ignoring white space. |
| 761 | Can be used multiple times, the last one encountered in a matching |
Bram Moolenaar | 13fcaaf | 2005-04-15 21:13:42 +0000 | [diff] [blame] | 762 | branch is used. Example: > |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 763 | /\(.\{-}\zsFab\)\{3} |
| 764 | < Finds the third occurrence of "Fab". |
| 765 | {not in Vi} {not available when compiled without the +syntax feature} |
| 766 | */\ze* |
| 767 | \ze Matches at any position, and sets the end of the match there: The |
| 768 | previous char is the last char of the whole match. |/zero-width| |
| 769 | Can be used multiple times, the last one encountered in a matching |
| 770 | branch is used. |
| 771 | Example: "end\ze\(if\|for\)" matches the "end" in "endif" and |
| 772 | "endfor". |
| 773 | {not in Vi} {not available when compiled without the +syntax feature} |
| 774 | |
| 775 | */\%^* *start-of-file* |
| 776 | \%^ Matches start of the file. When matching with a string, matches the |
| 777 | start of the string. {not in Vi} |
| 778 | For example, to find the first "VIM" in a file: > |
| 779 | /\%^\_.\{-}\zsVIM |
| 780 | < |
| 781 | */\%$* *end-of-file* |
| 782 | \%$ Matches end of the file. When matching with a string, matches the |
| 783 | end of the string. {not in Vi} |
| 784 | Note that this does NOT find the last "VIM" in a file: > |
| 785 | /VIM\_.\{-}\%$ |
| 786 | < It will find the next VIM, because the part after it will always |
| 787 | match. This one will find the last "VIM" in the file: > |
| 788 | /VIM\ze\(\(VIM\)\@!\_.\)*\%$ |
| 789 | < This uses |/\@!| to ascertain that "VIM" does NOT match in any |
| 790 | position after the first "VIM". |
| 791 | Searching from the end of the file backwards is easier! |
| 792 | |
Bram Moolenaar | 33aec76 | 2006-01-22 23:30:12 +0000 | [diff] [blame] | 793 | */\%V* |
| 794 | \%V Match inside the Visual area. When Visual mode has already been |
| 795 | stopped match in the area that |gv| would reselect. |
| 796 | Only works for the current buffer. |
| 797 | |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 798 | */\%#* *cursor-position* |
| 799 | \%# Matches with the cursor position. Only works when matching in a |
| 800 | buffer displayed in a window. {not in Vi} |
| 801 | WARNING: When the cursor is moved after the pattern was used, the |
| 802 | result becomes invalid. Vim doesn't automatically update the matches. |
| 803 | This is especially relevant for syntax highlighting and 'hlsearch'. |
| 804 | In other words: When the cursor moves the display isn't updated for |
| 805 | this change. An update is done for lines which are changed (the whole |
| 806 | line is updated) or when using the |CTRL-L| command (the whole screen |
| 807 | is updated). Example, to highlight the word under the cursor: > |
| 808 | /\k*\%#\k* |
| 809 | < When 'hlsearch' is set and you move the cursor around and make changes |
| 810 | this will clearly show when the match is updated or not. |
| 811 | |
Bram Moolenaar | 33aec76 | 2006-01-22 23:30:12 +0000 | [diff] [blame] | 812 | */\%'m* */\%<'m* */\%>'m* |
| 813 | \%'m Matches with the position of mark m. |
| 814 | \%<'m Matches before the position of mark m. |
| 815 | \%>'m Matches after the position of mark m. |
| 816 | Example, to highlight the text from mark 's to 'e: > |
| 817 | /.\%>'s.*\%<'e.. |
| 818 | < Note that two dots are required to include mark 'e in the match. That |
| 819 | is because "\%<'e" matches at the character before the 'e mark, and |
| 820 | since it's a |/zero-width| match it doesn't include that character. |
| 821 | {not in Vi} |
| 822 | WARNING: When the mark is moved after the pattern was used, the result |
| 823 | becomes invalid. Vim doesn't automatically update the matches. |
| 824 | Similar to moving the cursor for |\%#|. |
| 825 | |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 826 | */\%l* */\%>l* */\%<l* |
| 827 | \%23l Matches in a specific line. |
Bram Moolenaar | 4770d09 | 2006-01-12 23:22:24 +0000 | [diff] [blame] | 828 | \%<23l Matches above a specific line (lower line number). |
| 829 | \%>23l Matches below a specific line (higher line number). |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 830 | These three can be used to match specific lines in a buffer. The "23" |
| 831 | can be any line number. The first line is 1. {not in Vi} |
| 832 | WARNING: When inserting or deleting lines Vim does not automatically |
| 833 | update the matches. This means Syntax highlighting quickly becomes |
| 834 | wrong. |
| 835 | Example, to highlight the line where the cursor currently is: > |
| 836 | :exe '/\%' . line(".") . 'l.*' |
| 837 | < When 'hlsearch' is set and you move the cursor around and make changes |
| 838 | this will clearly show when the match is updated or not. |
| 839 | |
| 840 | */\%c* */\%>c* */\%<c* |
| 841 | \%23c Matches in a specific column. |
| 842 | \%<23c Matches before a specific column. |
| 843 | \%>23c Matches after a specific column. |
| 844 | These three can be used to match specific columns in a buffer or |
| 845 | string. The "23" can be any column number. The first column is 1. |
| 846 | Actually, the column is the byte number (thus it's not exactly right |
| 847 | for multi-byte characters). {not in Vi} |
| 848 | WARNING: When inserting or deleting text Vim does not automatically |
| 849 | update the matches. This means Syntax highlighting quickly becomes |
| 850 | wrong. |
| 851 | Example, to highlight the column where the cursor currently is: > |
| 852 | :exe '/\%' . col(".") . 'c' |
| 853 | < When 'hlsearch' is set and you move the cursor around and make changes |
| 854 | this will clearly show when the match is updated or not. |
| 855 | Example for matching a single byte in column 44: > |
| 856 | /\%>43c.\%<46c |
| 857 | < Note that "\%<46c" matches in column 45 when the "." matches a byte in |
| 858 | column 44. |
| 859 | */\%v* */\%>v* */\%<v* |
| 860 | \%23v Matches in a specific virtual column. |
| 861 | \%<23v Matches before a specific virtual column. |
| 862 | \%>23v Matches after a specific virtual column. |
| 863 | These three can be used to match specific virtual columns in a buffer |
| 864 | or string. When not matching with a buffer in a window, the option |
| 865 | values of the current window are used (e.g., 'tabstop'). |
| 866 | The "23" can be any column number. The first column is 1. |
| 867 | Note that some virtual column positions will never match, because they |
| 868 | are halfway a Tab or other character that occupies more than one |
| 869 | screen character. {not in Vi} |
| 870 | WARNING: When inserting or deleting text Vim does not automatically |
Bram Moolenaar | de934d7 | 2005-05-22 22:09:40 +0000 | [diff] [blame] | 871 | update highlighted matches. This means Syntax highlighting quickly |
| 872 | becomes wrong. |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 873 | Example, to highlight the all characters after virtual column 72: > |
| 874 | /\%>72v.* |
| 875 | < When 'hlsearch' is set and you move the cursor around and make changes |
| 876 | this will clearly show when the match is updated or not. |
| 877 | To match the text up to column 17: > |
| 878 | /.*\%17v |
| 879 | < Column 17 is not included, because that's where the "\%17v" matches, |
| 880 | and since this is a |/zero-width| match, column 17 isn't included in |
| 881 | the match. This does the same: > |
| 882 | /.*\%<18v |
| 883 | < |
| 884 | |
| 885 | Character classes: {not in Vi} |
| 886 | \i identifier character (see 'isident' option) */\i* |
| 887 | \I like "\i", but excluding digits */\I* |
| 888 | \k keyword character (see 'iskeyword' option) */\k* |
| 889 | \K like "\k", but excluding digits */\K* |
| 890 | \f file name character (see 'isfname' option) */\f* |
| 891 | \F like "\f", but excluding digits */\F* |
| 892 | \p printable character (see 'isprint' option) */\p* |
| 893 | \P like "\p", but excluding digits */\P* |
| 894 | |
| 895 | NOTE: the above also work for multi-byte characters. The ones below only |
| 896 | match ASCII characters, as indicated by the range. |
| 897 | |
| 898 | *whitespace* *white-space* |
| 899 | \s whitespace character: <Space> and <Tab> */\s* |
| 900 | \S non-whitespace character; opposite of \s */\S* |
| 901 | \d digit: [0-9] */\d* |
| 902 | \D non-digit: [^0-9] */\D* |
| 903 | \x hex digit: [0-9A-Fa-f] */\x* |
| 904 | \X non-hex digit: [^0-9A-Fa-f] */\X* |
| 905 | \o octal digit: [0-7] */\o* |
| 906 | \O non-octal digit: [^0-7] */\O* |
| 907 | \w word character: [0-9A-Za-z_] */\w* |
| 908 | \W non-word character: [^0-9A-Za-z_] */\W* |
| 909 | \h head of word character: [A-Za-z_] */\h* |
| 910 | \H non-head of word character: [^A-Za-z_] */\H* |
| 911 | \a alphabetic character: [A-Za-z] */\a* |
| 912 | \A non-alphabetic character: [^A-Za-z] */\A* |
| 913 | \l lowercase character: [a-z] */\l* |
| 914 | \L non-lowercase character: [^a-z] */\L* |
| 915 | \u uppercase character: [A-Z] */\u* |
| 916 | \U non-uppercase character [^A-Z] */\U* |
| 917 | |
| 918 | NOTE: Using the atom is faster than the [] form. |
| 919 | |
| 920 | NOTE: 'ignorecase', "\c" and "\C" are not used by character classes. |
| 921 | |
| 922 | */\_* *E63* */\_i* */\_I* */\_k* */\_K* */\_f* */\_F* |
| 923 | */\_p* */\_P* */\_s* */\_S* */\_d* */\_D* */\_x* */\_X* |
| 924 | */\_o* */\_O* */\_w* */\_W* */\_h* */\_H* */\_a* */\_A* |
| 925 | */\_l* */\_L* */\_u* */\_U* |
| 926 | \_x Where "x" is any of the characters above: The character class with |
| 927 | end-of-line added |
| 928 | (end of character classes) |
| 929 | |
| 930 | \e matches <Esc> */\e* |
| 931 | \t matches <Tab> */\t* |
| 932 | \r matches <CR> */\r* |
| 933 | \b matches <BS> */\b* |
| 934 | \n matches an end-of-line */\n* |
| 935 | When matching in a string instead of buffer text a literal newline |
| 936 | character is matched. |
| 937 | |
| 938 | ~ matches the last given substitute string */~* */\~* |
| 939 | |
| 940 | \(\) A pattern enclosed by escaped parentheses. */\(* */\(\)* */\)* |
| 941 | E.g., "\(^a\)" matches 'a' at the start of a line. *E51* *E54* *E55* |
| 942 | |
| 943 | \1 Matches the same string that was matched by */\1* *E65* |
| 944 | the first sub-expression in \( and \). {not in Vi} |
| 945 | Example: "\([a-z]\).\1" matches "ata", "ehe", "tot", etc. |
| 946 | \2 Like "\1", but uses second sub-expression, */\2* |
| 947 | ... */\3* |
| 948 | \9 Like "\1", but uses ninth sub-expression. */\9* |
| 949 | Note: The numbering of groups is done based on which "\(" comes first |
| 950 | in the pattern (going left to right), NOT based on what is matched |
| 951 | first. |
| 952 | |
| 953 | \%(\) A pattern enclosed by escaped parentheses. */\%(\)* */\%(* *E53* |
| 954 | Just like \(\), but without counting it as a sub-expression. This |
| 955 | allows using more groups and it's a little bit faster. |
| 956 | {not in Vi} |
| 957 | |
| 958 | x A single character, with no special meaning, matches itself |
| 959 | |
| 960 | */\* */\\* |
| 961 | \x A backslash followed by a single character, with no special meaning, |
| 962 | is reserved for future expansions |
| 963 | |
| 964 | [] (with 'nomagic': \[]) */[]* */\[]* */\_[]* */collection* |
| 965 | \_[] |
Bram Moolenaar | 13fcaaf | 2005-04-15 21:13:42 +0000 | [diff] [blame] | 966 | A collection. This is a sequence of characters enclosed in brackets. |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 967 | It matches any single character in the collection. |
| 968 | Example matches ~ |
| 969 | [xyz] any 'x', 'y' or 'z' |
| 970 | [a-zA-Z]$ any alphabetic character at the end of a line |
| 971 | \c[a-z]$ same |
| 972 | |
| 973 | With "\_" prepended the collection also includes the end-of-line. |
| 974 | The same can be done by including "\n" in the collection. The |
| 975 | end-of-line is also matched when the collection starts with "^"! Thus |
| 976 | "\_[^ab]" matches the end-of-line and any character but "a" and "b". |
| 977 | This makes it Vi compatible: Without the "\_" or "\n" the collection |
| 978 | does not match an end-of-line. |
Bram Moolenaar | 8aff23a | 2005-08-19 20:40:30 +0000 | [diff] [blame] | 979 | *E769* |
Bram Moolenaar | ae5bce1 | 2005-08-15 21:41:48 +0000 | [diff] [blame] | 980 | When the ']' is not there Vim will not give an error message but |
Bram Moolenaar | 8aff23a | 2005-08-19 20:40:30 +0000 | [diff] [blame] | 981 | assume no collection is used. Useful to search for '['. However, you |
| 982 | do get E769 for internal searching. |
Bram Moolenaar | ae5bce1 | 2005-08-15 21:41:48 +0000 | [diff] [blame] | 983 | |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 984 | If the sequence begins with "^", it matches any single character NOT |
| 985 | in the collection: "[^xyz]" matches anything but 'x', 'y' and 'z'. |
| 986 | - If two characters in the sequence are separated by '-', this is |
| 987 | shorthand for the full list of ASCII characters between them. E.g., |
| 988 | "[0-9]" matches any decimal digit. |
| 989 | - A character class expression is evaluated to the set of characters |
| 990 | belonging to that character class. The following character classes |
| 991 | are supported: |
| 992 | Name Contents ~ |
| 993 | *[:alnum:]* [:alnum:] letters and digits |
| 994 | *[:alpha:]* [:alpha:] letters |
| 995 | *[:blank:]* [:blank:] space and tab characters |
| 996 | *[:cntrl:]* [:cntrl:] control characters |
| 997 | *[:digit:]* [:digit:] decimal digits |
| 998 | *[:graph:]* [:graph:] printable characters excluding space |
| 999 | *[:lower:]* [:lower:] lowercase letters (all letters when |
| 1000 | 'ignorecase' is used) |
| 1001 | *[:print:]* [:print:] printable characters including space |
| 1002 | *[:punct:]* [:punct:] punctuation characters |
| 1003 | *[:space:]* [:space:] whitespace characters |
| 1004 | *[:upper:]* [:upper:] uppercase letters (all letters when |
| 1005 | 'ignorecase' is used) |
| 1006 | *[:xdigit:]* [:xdigit:] hexadecimal digits |
| 1007 | *[:return:]* [:return:] the <CR> character |
| 1008 | *[:tab:]* [:tab:] the <Tab> character |
| 1009 | *[:escape:]* [:escape:] the <Esc> character |
| 1010 | *[:backspace:]* [:backspace:] the <BS> character |
| 1011 | The brackets in character class expressions are additional to the |
| 1012 | brackets delimiting a collection. For example, the following is a |
| 1013 | plausible pattern for a UNIX filename: "[-./[:alnum:]_~]\+" That is, |
| 1014 | a list of at least one character, each of which is either '-', '.', |
| 1015 | '/', alphabetic, numeric, '_' or '~'. |
| 1016 | These items only work for 8-bit characters. |
Bram Moolenaar | 26a60b4 | 2005-02-22 08:49:11 +0000 | [diff] [blame] | 1017 | */[[=* *[==]* |
| 1018 | - An equivalence class. This means that characters are matched that |
| 1019 | have almost the same meaning, e.g., when ignoring accents. The form |
| 1020 | is: |
| 1021 | [=a=] |
| 1022 | Currrently this is only implemented for latin1. Also works for the |
| 1023 | latin1 characters in utf-8 and latin9. |
| 1024 | */[[.* *[..]* |
| 1025 | - A collation element. This currently simply accepts a single |
| 1026 | character in the form: |
| 1027 | [.a.] |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 1028 | */\]* |
| 1029 | - To include a literal ']', '^', '-' or '\' in the collection, put a |
| 1030 | backslash before it: "[xyz\]]", "[\^xyz]", "[xy\-z]" and "[xyz\\]". |
| 1031 | (Note: POSIX does not support the use of a backslash this way). For |
| 1032 | ']' you can also make it the first character (following a possible |
| 1033 | "^"): "[]xyz]" or "[^]xyz]" {not in Vi}. |
| 1034 | For '-' you can also make it the first or last character: "[-xyz]", |
| 1035 | "[^-xyz]" or "[xyz-]". For '\' you can also let it be followed by |
| 1036 | any character that's not in "^]-\bertn". "[\xyz]" matches '\', 'x', |
| 1037 | 'y' and 'z'. It's better to use "\\" though, future expansions may |
| 1038 | use other characters after '\'. |
| 1039 | - The following translations are accepted when the 'l' flag is not |
| 1040 | included in 'cpoptions' {not in Vi}: |
| 1041 | \e <Esc> |
| 1042 | \t <Tab> |
| 1043 | \r <CR> (NOT end-of-line!) |
| 1044 | \b <BS> |
Bram Moolenaar | c0197e2 | 2004-09-13 20:26:32 +0000 | [diff] [blame] | 1045 | \d123 decimal number of character |
| 1046 | \o40 octal number of character up to 0377 |
| 1047 | \x20 hexadecimal number of character up to 0xff |
| 1048 | \u20AC hex. number of multibyte character up to 0xffff |
| 1049 | \U1234 hex. number of multibyte character up to 0xffffffff |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 1050 | NOTE: The other backslash codes mentioned above do not work inside |
| 1051 | []! |
| 1052 | - Matching with a collection can be slow, because each character in |
| 1053 | the text has to be compared with each character in the collection. |
| 1054 | Use one of the other atoms above when possible. Example: "\d" is |
| 1055 | much faster than "[0-9]" and matches the same characters. |
| 1056 | |
| 1057 | */\%[]* *E69* *E70* *E369* |
Bram Moolenaar | c0197e2 | 2004-09-13 20:26:32 +0000 | [diff] [blame] | 1058 | \%[] A sequence of optionally matched atoms. This always matches. |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 1059 | It matches as much of the list of atoms it contains as possible. Thus |
| 1060 | it stops at the first atom that doesn't match. For example: > |
| 1061 | /r\%[ead] |
| 1062 | < matches "r", "re", "rea" or "read". The longest that matches is used. |
| 1063 | To match the Ex command "function", where "fu" is required and |
| 1064 | "nction" is optional, this would work: > |
| 1065 | /\<fu\%[nction]\> |
| 1066 | < The end-of-word atom "\>" is used to avoid matching "fu" in "full". |
| 1067 | It gets more complicated when the atoms are not ordinary characters. |
| 1068 | You don't often have to use it, but it is possible. Example: > |
| 1069 | /\<r\%[[eo]ad]\> |
| 1070 | < Matches the words "r", "re", "ro", "rea", "roa", "read" and "road". |
| 1071 | {not available when compiled without the +syntax feature} |
| 1072 | |
Bram Moolenaar | 677ee68 | 2005-01-27 14:41:15 +0000 | [diff] [blame] | 1073 | */\%d* */\%x* */\%o* */\%u* */\%U* *E678* |
Bram Moolenaar | c0197e2 | 2004-09-13 20:26:32 +0000 | [diff] [blame] | 1074 | |
| 1075 | \%d123 Matches the character specified with a decimal number. Must be |
| 1076 | followed by a non-digit. |
| 1077 | \%o40 Matches the character specified with an octal number up to 0377. |
| 1078 | Numbers below 040 must be followed by a non-octal digit or a non-digit. |
| 1079 | \%x2a Matches the character specified with up to two hexadecimal characters. |
| 1080 | \%u20AC Matches the character specified with up to four hexadecimal |
| 1081 | characters. |
| 1082 | \%U1234abcd Matches the character specified with up to eight hexadecimal |
| 1083 | characters. |
Bram Moolenaar | 071d427 | 2004-06-13 20:20:40 +0000 | [diff] [blame] | 1084 | |
| 1085 | ============================================================================== |
| 1086 | 7. Ignoring case in a pattern */ignorecase* |
| 1087 | |
| 1088 | If the 'ignorecase' option is on, the case of normal letters is ignored. |
| 1089 | 'smartcase' can be set to ignore case when the pattern contains lowercase |
| 1090 | letters only. |
| 1091 | */\c* */\C* |
| 1092 | When "\c" appears anywhere in the pattern, the whole pattern is handled like |
| 1093 | 'ignorecase' is on. The actual value of 'ignorecase' and 'smartcase' is |
| 1094 | ignored. "\C" does the opposite: Force matching case for the whole pattern. |
| 1095 | {only Vim supports \c and \C} |
| 1096 | Note that 'ignorecase', "\c" and "\C" are not used for the character classes. |
| 1097 | |
| 1098 | Examples: |
| 1099 | pattern 'ignorecase' 'smartcase' matches ~ |
| 1100 | foo off - foo |
| 1101 | foo on - foo Foo FOO |
| 1102 | Foo on off foo Foo FOO |
| 1103 | Foo on on Foo |
| 1104 | \cfoo - - foo Foo FOO |
| 1105 | foo\C - - foo |
| 1106 | |
| 1107 | */\Z* |
| 1108 | When "\Z" appears anywhere in the pattern, composing characters are ignored. |
| 1109 | Thus only the base characters need to match, the composing characters may be |
| 1110 | different and the number of composing characters may differ. Only relevant |
| 1111 | when 'encoding' is "utf-8". |
| 1112 | |
| 1113 | Technical detail: *NL-used-for-Nul* |
| 1114 | <Nul> characters in the file are stored as <NL> in memory. In the display |
| 1115 | they are shown as "^@". The translation is done when reading and writing |
| 1116 | files. To match a <Nul> with a search pattern you can just enter CTRL-@ or |
| 1117 | "CTRL-V 000". This is probably just what you expect. Internally the |
| 1118 | character is replaced with a <NL> in the search pattern. What is unusual is |
| 1119 | that typing CTRL-V CTRL-J also inserts a <NL>, thus also searches for a <Nul> |
| 1120 | in the file. {Vi cannot handle <Nul> characters in the file at all} |
| 1121 | |
| 1122 | *CR-used-for-NL* |
| 1123 | When 'fileformat' is "mac", <NL> characters in the file are stored as <CR> |
| 1124 | characters internally. In the display they are shown as "^M". Otherwise this |
| 1125 | works similar to the usage of <NL> for a <Nul>. |
| 1126 | |
| 1127 | When working with expression evaluation, a <NL> character in the pattern |
| 1128 | matches a <NL> in the string. The use of "\n" (backslash n) to match a <NL> |
| 1129 | doesn't work there, it only works to match text in the buffer. |
| 1130 | |
| 1131 | *pattern-multi-byte* |
| 1132 | Patterns will also work with multi-byte characters, mostly as you would |
| 1133 | expect. But invalid bytes may cause trouble, a pattern with an invalid byte |
| 1134 | will probably never match. |
| 1135 | |
| 1136 | ============================================================================== |
| 1137 | 8. Compare with Perl patterns *perl-patterns* |
| 1138 | |
| 1139 | Vim's regexes are most similar to Perl's, in terms of what you can do. The |
| 1140 | difference between them is mostly just notation; here's a summary of where |
| 1141 | they differ: |
| 1142 | |
| 1143 | Capability in Vimspeak in Perlspeak ~ |
| 1144 | ---------------------------------------------------------------- |
| 1145 | force case insensitivity \c (?i) |
| 1146 | force case sensitivity \C (?-i) |
| 1147 | backref-less grouping \%(atom) (?:atom) |
| 1148 | conservative quantifiers \{-n,m} *?, +?, ??, {}? |
| 1149 | 0-width match atom\@= (?=atom) |
| 1150 | 0-width non-match atom\@! (?!atom) |
| 1151 | 0-width preceding match atom\@<= (?<=atom) |
| 1152 | 0-width preceding non-match atom\@<! (?<!atom) |
| 1153 | match without retry atom\@> (?>atom) |
| 1154 | |
| 1155 | Vim and Perl handle newline characters inside a string a bit differently: |
| 1156 | |
| 1157 | In Perl, ^ and $ only match at the very beginning and end of the text, |
| 1158 | by default, but you can set the 'm' flag, which lets them match at |
| 1159 | embedded newlines as well. You can also set the 's' flag, which causes |
| 1160 | a . to match newlines as well. (Both these flags can be changed inside |
| 1161 | a pattern using the same syntax used for the i flag above, BTW.) |
| 1162 | |
| 1163 | On the other hand, Vim's ^ and $ always match at embedded newlines, and |
| 1164 | you get two separate atoms, \%^ and \%$, which only match at the very |
| 1165 | start and end of the text, respectively. Vim solves the second problem |
| 1166 | by giving you the \_ "modifier": put it in front of a . or a character |
| 1167 | class, and they will match newlines as well. |
| 1168 | |
| 1169 | Finally, these constructs are unique to Perl: |
| 1170 | - execution of arbitrary code in the regex: (?{perl code}) |
| 1171 | - conditional expressions: (?(condition)true-expr|false-expr) |
| 1172 | |
| 1173 | ...and these are unique to Vim: |
| 1174 | - changing the magic-ness of a pattern: \v \V \m \M |
| 1175 | (very useful for avoiding backslashitis) |
| 1176 | - sequence of optionally matching atoms: \%[atoms] |
| 1177 | - \& (which is to \| what "and" is to "or"; it forces several branches |
| 1178 | to match at one spot) |
| 1179 | - matching lines/columns by number: \%5l \%5c \%5v |
| 1180 | - limiting the "return value" of a regex: \zs \ze |
| 1181 | |
| 1182 | ============================================================================== |
| 1183 | 9. Highlighting matches *match-highlight* |
| 1184 | |
| 1185 | *:mat* *:match* |
| 1186 | :mat[ch] {group} /{pattern}/ |
| 1187 | Define a pattern to highlight in the current window. It will |
| 1188 | be highlighted with {group}. Example: > |
| 1189 | :highlight MyGroup ctermbg=green guibg=green |
| 1190 | :match MyGroup /TODO/ |
| 1191 | < Instead of // any character can be used to mark the start and |
| 1192 | end of the {pattern}. Watch out for using special characters, |
| 1193 | such as '"' and '|'. |
| 1194 | {group} must exist at the moment this command is executed. |
| 1195 | The match overrides the 'hlsearch' highlighting. |
| 1196 | 'ignorecase' does not apply, use |/\c| in the pattern to |
| 1197 | ignore case. Otherwise case is not ignored. |
| 1198 | Note that highlighting the last used search pattern with |
| 1199 | 'hlsearch' is used in all windows, while the pattern defined |
| 1200 | with ":match" only exists in the current window. It is kept |
| 1201 | when switching to another buffer. |
| 1202 | Another example, which highlights all characters in virtual |
| 1203 | column 72 and more: > |
| 1204 | :highlight rightMargin term=bold ctermfg=blue guifg=blue |
| 1205 | :match rightMargin /.\%>72v/ |
| 1206 | < To highlight all character that are in virtual column 7: > |
| 1207 | :highlight col8 ctermbg=grey guibg=grey |
| 1208 | :match col8 /\%<8v.\%>7v/ |
| 1209 | < Note the use of two items to also match a character that |
| 1210 | occupies more than one virtual column, such as a TAB. |
| 1211 | |
| 1212 | :mat[ch] |
| 1213 | :mat[ch] none |
| 1214 | Clear a previously defined match pattern. |
| 1215 | |
| 1216 | vim:tw=78:ts=8:ft=help:norl: |