Mercurial > vim

comparison runtime/doc/quickfix.txt @ 43:f55897d6921d v7.0026

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
updated for version 7.0026
author vimboss
date Wed, 29 Dec 2004 21:03:02 +0000
parents f529edb9bab3
children 8173ec1e9f1f
comparison
equal deleted inserted replaced
42:c75153d791d0 43:f55897d6921d
1 *quickfix.txt* For Vim version 7.0aa. Last change: 2004 Dec 27 1 *quickfix.txt* For Vim version 7.0aa. Last change: 2004 Dec 28
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
279 Vim has two ways to find matches for a pattern: Internal and external. The 279 Vim has two ways to find matches for a pattern: Internal and external. The
280 advantage of the internal grep is that it works on all systems and uses the 280 advantage of the internal grep is that it works on all systems and uses the
281 powerful Vim search patterns. An external grep program can be used when the 281 powerful Vim search patterns. An external grep program can be used when the
282 Vim grep does not do what you want. 282 Vim grep does not do what you want.
283 283
284 The internal method may be a bit slower, because files are read into memory. 284 The internal method will be slower, because files are read into memory. The
285 The advantage is that line separators and encoding are automatically 285 advantages are:
286 recognized, as if a file is being edited. And multi-line patterns can be 286 - Line separators and encoding are automatically recognized, as if a file is
287 used. 287 being edited.
288 - Uses Vim search patterns. Multi-line patterns can be used.
289 - When plugins are enabled: compressed and remote files can be searched.
290 |gzip| |netrw|
288 291
289 292
290 5.1 using Vim's internal grep 293 5.1 using Vim's internal grep
291 294
292 *:vim* *:vimgrep* 295 *:vim* *:vimgrep*
293 :vim[grep][!] /{pattern}/ {file} ... 296 :vim[grep][!] /{pattern}/ {file} ...
294 Search for {pattern} in the files {file} ... and set 297 Search for {pattern} in the files {file} ... and set
295 the error list to the matches. 298 the error list to the matches.
296 {pattern} if a Vim search pattern. Instead of 299 {pattern} if a Vim search pattern. Instead of
297 enclosing it in / any character can be used, so long 300 enclosing it in / any non-ID character |'isident'|
298 as it does not appear in {pattern}. 301 can be used, so long as it does not appear in
299 302 {pattern}.
303 Examples: >
304 :vimgrep /an error/ *.c
305 :vimgrep /\<FileName\>/ *.h include/*
306
307 :vim[grep][!] {pattern} {file} ...
308 Like above, but instead of enclosing the pattern in a
309 non-ID character use a white-separated pattern. The
310 pattern must start with an ID character.
311 Example: >
312 :vimgrep Error *.c
313 <
300 *:vimgrepa* *:vimgrepadd* 314 *:vimgrepa* *:vimgrepadd*
301 :vimgrepa[dd][!] /{pattern}/ {file} ... 315 :vimgrepa[dd][!] [/]{pattern}[/] {file} ...
302 Just like ":vimgrep", but instead of making a new list 316 Just like ":vimgrep", but instead of making a new list
303 of errors the matches are appended to the current 317 of errors the matches are appended to the current
304 list. 318 list.
305 319
306 320