Mercurial > vim
comparison runtime/doc/quickfix.txt @ 7:3fc0f57ecb91 v7.0001
updated for version 7.0001
author | vimboss |
---|---|
date | Sun, 13 Jun 2004 20:20:40 +0000 |
parents | |
children | 4102fb4ea781 |
comparison
equal
deleted
inserted
replaced
6:c2daee826b8f | 7:3fc0f57ecb91 |
---|---|
1 *quickfix.txt* For Vim version 7.0aa. Last change: 2004 May 20 | |
2 | |
3 | |
4 VIM REFERENCE MANUAL by Bram Moolenaar | |
5 | |
6 | |
7 This subject is introduced in section |30.1| of the user manual. | |
8 | |
9 1. Using QuickFix commands |quickfix| | |
10 2. The error window |quickfix-window| | |
11 3. Using more than one list of errors |quickfix-error-lists| | |
12 4. Using :make |:make_makeprg| | |
13 5. Using :grep |grep| | |
14 6. Selecting a compiler |compiler-select| | |
15 7. The error format |error-file-format| | |
16 8. The directory stack |quickfix-directory-stack| | |
17 9. Specific error file formats |errorformats| | |
18 | |
19 {Vi does not have any of these commands} | |
20 | |
21 The quickfix commands are not available when the |+quickfix| feature was | |
22 disabled at compile time. | |
23 | |
24 ============================================================================= | |
25 1. Using QuickFix commands *quickfix* *Quickfix* *E42* | |
26 | |
27 Vim has a special mode to speedup the edit-compile-edit cycle. This is | |
28 inspired by the quickfix option of the Manx's Aztec C compiler on the Amiga. | |
29 The idea is to save the error messages from the compiler in a file and use Vim | |
30 to jump to the errors one by one. You can examine each problem and fix it, | |
31 without having to remember all the error messages. | |
32 | |
33 If you are using Manx's Aztec C compiler on the Amiga look here for how to use | |
34 it with Vim: |quickfix-manx|. If you are using another compiler you should | |
35 save the error messages in a file and start Vim with "vim -q filename". An | |
36 easy way to do this is with the |:make| command (see below). The | |
37 'errorformat' option should be set to match the error messages from your | |
38 compiler (see |errorformat| below). | |
39 | |
40 The following quickfix commands can be used: | |
41 | |
42 *:cc* | |
43 :cc[!] [nr] Display error [nr]. If [nr] is omitted, the same | |
44 error is displayed again. Without [!] this doesn't | |
45 work when jumping to another buffer, the current buffer | |
46 has been changed, there is the only window for the | |
47 buffer and both 'hidden' and 'autowrite' are off. | |
48 When jumping to another buffer with [!] any changes to | |
49 the current buffer are lost, unless 'hidden' is set or | |
50 there is another window for this buffer. | |
51 The 'switchbuf' settings are respected when jumping | |
52 to a buffer. | |
53 | |
54 *:cn* *:cnext* *E553* | |
55 :[count]cn[ext][!] Display the [count] next error in the list that | |
56 includes a file name. If there are no file names at | |
57 all, go to the [count] next error. See |:cc| for | |
58 [!] and 'switchbuf'. | |
59 | |
60 :[count]cN[ext][!] *:cp* *:cprevious* *:cN* *:cNext* | |
61 :[count]cp[revious][!] Display the [count] previous error in the list that | |
62 includes a file name. If there are no file names at | |
63 all, go to the [count] previous error. See |:cc| for | |
64 [!] and 'switchbuf'. | |
65 | |
66 *:cnf* *:cnfile* | |
67 :[count]cnf[ile][!] Display the first error in the [count] next file in | |
68 the list that includes a file name. If there are no | |
69 file names at all or if there is no next file, go to | |
70 the [count] next error. See |:cc| for [!] and | |
71 'switchbuf'. | |
72 | |
73 :[count]cNf[ile][!] *:cpf* *:cpfile* *:cNf* *:cNfile* | |
74 :[count]cpf[ile][!] Display the last error in the [count] previous file in | |
75 the list that includes a file name. If there are no | |
76 file names at all or if there is no next file, go to | |
77 the [count] previous error. See |:cc| for [!] and | |
78 'switchbuf'. | |
79 | |
80 *:crewind* *:cr* | |
81 :cr[ewind][!] [nr] Display error [nr]. If [nr] is omitted, the FIRST | |
82 error is displayed. See |:cc|. | |
83 | |
84 *:cfirst* *:cfir* | |
85 :cfir[st][!] [nr] Same as ":crewind". | |
86 | |
87 *:clast* *:cla* | |
88 :cla[st][!] [nr] Display error [nr]. If [nr] is omitted, the LAST | |
89 error is displayed. See |:cc|. | |
90 | |
91 *:cq* *:cquit* | |
92 :cq[uit] Quit Vim with an error code, so that the compiler | |
93 will not compile the same file again. | |
94 | |
95 *:cf* *:cfile* | |
96 :cf[ile][!] [errorfile] Read the error file and jump to the first error. | |
97 This is done automatically when Vim is started with | |
98 the -q option. You can use this command when you | |
99 keep Vim running while compiling. If you give the | |
100 name of the errorfile, the 'errorfile' option will | |
101 be set to [errorfile]. See |:cc| for [!]. | |
102 | |
103 *:cg* *:cgetfile* | |
104 :cg[etfile][!] [errorfile] | |
105 Read the error file. Just like ":cfile" but don't | |
106 jump to the first error. | |
107 | |
108 *:cl* *:clist* | |
109 :cl[ist] [from] [, [to]] | |
110 List all errors that are valid |quickfix-valid|. | |
111 If numbers [from] and/or [to] are given, the respective | |
112 range of errors is listed. A negative number counts | |
113 from the last error backwards, -1 being the last error. | |
114 The 'switchbuf' settings are respected when jumping | |
115 to a buffer. | |
116 | |
117 :cl[ist]! [from] [, [to]] | |
118 List all errors. | |
119 | |
120 If you insert or delete lines, mostly the correct error location is still | |
121 found because hidden marks are used. Sometimes, when the mark has been | |
122 deleted for some reason, the message "line changed" is shown to warn you that | |
123 the error location may not be correct. If you quit Vim and start again the | |
124 marks are lost and the error locations may not be correct anymore. | |
125 | |
126 ============================================================================= | |
127 2. The error window *quickfix-window* | |
128 | |
129 *:cope* *:copen* | |
130 :cope[n] [height] Open a window to show the current list of errors. | |
131 When [height] is given, the window becomes that high | |
132 (if there is room). Otherwise the window is made ten | |
133 lines high. | |
134 The window will contain a special buffer, with | |
135 'buftype' equal to "quickfix". Don't change this! | |
136 If there already is a quickfix window, it will be made | |
137 the current window. It is not possible to open a | |
138 second quickfix window. | |
139 | |
140 *:ccl* *:cclose* | |
141 :ccl[ose] Close the quickfix window. | |
142 | |
143 *:cw* *:cwindow* | |
144 :cw[indow] [height] Open the quickfix window when there are recognized | |
145 errors. If the window is already open and there are | |
146 no recognized errors, close the window. | |
147 | |
148 | |
149 Normally the quickfix window is at the bottom of the screen. If there are | |
150 vertical splits, it's at the bottom of the rightmost column of windows. To | |
151 make it always occupy the full width: > | |
152 :botright cwindow | |
153 You can move the window around with |window-moving| commands. | |
154 For example, to move it to the top: CTRL-W K | |
155 The 'winfixheight' option will be set, which means that the window will mostly | |
156 keep its height, ignoring 'winheight' and 'equalalways'. You can change the | |
157 height manually (e.g., by dragging the status line above it with the mouse). | |
158 | |
159 In the quickfix window, each line is one error. The line number is equal to | |
160 the error number. You can use ":.cc" to jump to the error under the cursor. | |
161 Hitting the <CR> key or double-clicking the mouse on a line has the same | |
162 effect. The file containing the error is opened in the window above the | |
163 quickfix window. If there already is a window for that file, it is used | |
164 instead. If the buffer in the used window has changed, and the error is in | |
165 another file, jumping to the error will fail. You will first have to make | |
166 sure the window contains a buffer which can be abandoned. | |
167 | |
168 When the quickfix window has been filled, two autocommand events are | |
169 triggered. First the 'filetype' option is set to "qf", which triggers the | |
170 FileType event. Then the BufReadPost event is triggered. This can be used to | |
171 perform some action on the listed errors. Example: > | |
172 au BufReadPost quickfix setlocal nomodifiable | |
173 \ | silent g/^/s//\=line(".")." "/ | |
174 \ | setlocal modifiable | |
175 This prepends the line number to each line. Note the use of "\=" in the | |
176 substitute string of the ":s" command, which is used to evaluate an | |
177 expression. | |
178 | |
179 Note: Making changes in the quickfix window has no effect on the list of | |
180 errors. 'modifiable' is off to avoid making changes. If you delete or insert | |
181 lines anyway, the relation between the text and the error number is messed up. | |
182 If you really want to do this, you could write the contents of the quickfix | |
183 window to a file and use ":cfile" to have it parsed and used as the new error | |
184 list. | |
185 | |
186 ============================================================================= | |
187 3. Using more than one list of errors *quickfix-error-lists* | |
188 | |
189 So far has been assumed that there is only one list of errors. Actually the | |
190 ten last used lists are remembered. When starting a new list, the previous | |
191 ones are automatically kept. Two commands can be used to access older error | |
192 lists. They set one of the existing error lists as the current one. | |
193 | |
194 *:colder* *:col* *E380* | |
195 :col[der] [count] Go to older error list. When [count] is given, do | |
196 this [count] times. When already at the oldest error | |
197 list, an error message is given. | |
198 | |
199 *:cnewer* *:cnew* *E381* | |
200 :cnew[er] [count] Go to newer error list. When [count] is given, do | |
201 this [count] times. When already at the newest error | |
202 list, an error message is given. | |
203 | |
204 When adding a new error list, it becomes the current list. | |
205 | |
206 When ":colder" has been used and ":make" or ":grep" is used to add a new error | |
207 list, one newer list is overwritten. This is especially useful if you are | |
208 browsing with ":grep" |grep|. If you want to keep the more recent error | |
209 lists, use ":cnewer 99" first. | |
210 | |
211 ============================================================================= | |
212 4. Using :make *:make_makeprg* | |
213 | |
214 *:mak* *:make* | |
215 :mak[e][!] [arguments] 1. If the 'autowrite' option is on, write any changed | |
216 buffers | |
217 2. An errorfile name is made from 'makeef'. If | |
218 'makeef' doesn't contain "##", and a file with this | |
219 name already exists, it is deleted. | |
220 3. The program given with the 'makeprg' option is | |
221 started (default "make") with the optional | |
222 [arguments] and the output is saved in the | |
223 errorfile (for Unix it is also echoed on the | |
224 screen). | |
225 4. The errorfile is read using 'errorformat'. | |
226 5. If [!] is not given the first error is jumped to. | |
227 6. The errorfile is deleted. | |
228 7. You can now move through the errors with commands | |
229 like |:cnext| and |:cprevious|, see above. | |
230 This command does not accept a comment, any " | |
231 characters are considered part of the arguments. | |
232 | |
233 The ":make" command executes the command given with the 'makeprg' option. | |
234 This is done by passing the command to the shell given with the 'shell' | |
235 option. This works almost like typing | |
236 | |
237 ":!{makeprg} [arguments] {shellpipe} {errorfile}". | |
238 | |
239 {makeprg} is the string given with the 'makeprg' option. Any command can be | |
240 used, not just "make". Characters '%' and '#' are expanded as usual on a | |
241 command-line. You can use "%<" to insert the current file name without | |
242 extension, or "#<" to insert the alternate file name without extension, for | |
243 example: > | |
244 :set makeprg=make\ #<.o | |
245 | |
246 [arguments] is anything that is typed after ":make". | |
247 {shellpipe} is the 'shellpipe' option. | |
248 {errorfile} is the 'makeef' option, with ## replaced to make it unique. | |
249 | |
250 The placeholder "$*" can be used for the argument list in {makeprog} if the | |
251 command needs some additional characters after its arguments. The $* is | |
252 replaced then by all arguments. Example: > | |
253 :set makeprg=latex\ \\\\nonstopmode\ \\\\input\\{$*} | |
254 or simpler > | |
255 :let &mp = 'latex \\nonstopmode \\input\{$*}' | |
256 "$*" can be given multiple times, for example: > | |
257 :set makeprg=gcc\ -o\ $*\ $* | |
258 | |
259 The 'shellpipe' option defaults to ">" for the Amiga, MS-DOS and Win32. This | |
260 means that the output of the compiler is saved in a file and not shown on the | |
261 screen directly. For Unix "| tee" is used. The compiler output is shown on | |
262 the screen and saved in a file the same time. Depending on the shell used | |
263 "|& tee" or "2>&1| tee" is the default, so stderr output will be included. | |
264 | |
265 If 'shellpipe' is empty, the {errorfile} part will be omitted. This is useful | |
266 for compilers that write to an errorfile themselves (e.g., Manx's Amiga C). | |
267 | |
268 ============================================================================== | |
269 5. Using :grep *grep* *lid* | |
270 | |
271 Vim can interface with "grep" and grep-like programs (such as the GNU | |
272 id-utils) in a similar way to its compiler integration (see |:make| above). | |
273 | |
274 [Unix trivia: The name for the Unix "grep" command comes from ":g/re/p", where | |
275 "re" stands for Regular Expression.] | |
276 | |
277 *:gr* *:grep* | |
278 :gr[ep][!] [arguments] Just like ":make", but use 'grepprg' instead of | |
279 'makeprg' and 'grepformat' instead of 'errorformat'. | |
280 *:grepa* *:grepadd* | |
281 :grepa[dd][!] [arguments] | |
282 Just like ":grep", but instead of making a new list of | |
283 errors the matches are appended to the current list. | |
284 Example: > | |
285 :grep nothing % | |
286 :bufdo grepadd! something % | |
287 < The first command makes a new error list which is | |
288 empty. The second command executes "grepadd" for each | |
289 listed buffer. Note the use of ! to avoid that | |
290 ":grepadd" jumps to the first error, which is not | |
291 allowed with |:bufdo|. | |
292 | |
293 5.1 Setting up grep | |
294 | |
295 If you have a standard "grep" program installed, the :grep command may work | |
296 well with the defaults. The syntax is very similar to the standard command: > | |
297 | |
298 :grep foo *.c | |
299 | |
300 Will search all files with the .c extension for the substring "foo". The | |
301 arguments to :grep are passed straight to the "grep" program, so you can use | |
302 whatever options your "grep" supports. | |
303 | |
304 By default, :grep invokes grep with the -n option (show file and line | |
305 numbers). You can change this with the 'grepprg' option. You will need to set | |
306 'grepprg' if: | |
307 | |
308 a) You are using a program that isn't called "grep" | |
309 b) You have to call grep with a full path | |
310 c) You want to pass other options automatically (e.g. case insensitive | |
311 search.) | |
312 | |
313 Once "grep" has executed, Vim parses the results using the 'grepformat' | |
314 option. This option works in the same way as the 'errorformat' option - see | |
315 that for details. You may need to change 'grepformat' from the default if | |
316 your grep outputs in a non-standard format, or you are using some other | |
317 program with a special format. | |
318 | |
319 Once the results are parsed, Vim loads the first file containing a match and | |
320 jumps to the appropriate line, in the same way that it jumps to a compiler | |
321 error in |quickfix| mode. You can then use the |:cnext|, |:clist|, etc. | |
322 commands to see the other matches. | |
323 | |
324 | |
325 5.2 Using :grep with id-utils | |
326 | |
327 You can set up :grep to work with the GNU id-utils like this: > | |
328 | |
329 :set grepprg=lid\ -Rgrep\ -s | |
330 :set grepformat=%f:%l:%m | |
331 | |
332 then > | |
333 :grep (regexp) | |
334 | |
335 works just as you'd expect. | |
336 (provided you remembered to mkid first :) | |
337 | |
338 | |
339 5.3 Browsing source code with :grep | |
340 | |
341 Using the stack of error lists that Vim keeps, you can browse your files to | |
342 look for functions and the functions they call. For example, suppose that you | |
343 have to add an argument to the read_file() function. You enter this command: > | |
344 | |
345 :grep read_file *.c | |
346 | |
347 You use ":cn" to go along the list of matches and add the argument. At one | |
348 place you have to get the new argument from a higher level function msg(), and | |
349 need to change that one too. Thus you use: > | |
350 | |
351 :grep msg *.c | |
352 | |
353 While changing the msg() functions, you find another function that needs to | |
354 get the argument from a higher level. You can again use ":grep" to find these | |
355 functions. Once you are finished with one function, you can use > | |
356 | |
357 :colder | |
358 | |
359 to go back to the previous one. | |
360 | |
361 This works like browsing a tree: ":grep" goes one level deeper, creating a | |
362 list of branches. ":colder" goes back to the previous level. You can mix | |
363 this use of ":grep" and "colder" to browse all the locations in a tree-like | |
364 way. If you do this consistently, you will find all locations without the | |
365 need to write down a "todo" list. | |
366 | |
367 ============================================================================= | |
368 6. Selecting a compiler *compiler-select* | |
369 | |
370 *:comp* *:compiler* *E666* | |
371 :comp[iler][!] {name} Set options to work with compiler {name}. | |
372 Without the "!" options are set for the | |
373 current buffer. With "!" global options are | |
374 set. | |
375 If you use ":compiler foo" in "file.foo" and | |
376 then ":compiler! bar" in another buffer, Vim | |
377 will keep on using "foo" in "file.foo". | |
378 {not available when compiled without the | |
379 |+eval| feature} | |
380 | |
381 | |
382 The Vim plugins in the "compiler" directory will set options to use the | |
383 selected compiler. For ":compiler" local options are set, for ":compiler!" | |
384 global options. | |
385 *current_compiler* | |
386 To support older Vim versions, the plugins always use "current_compiler" and | |
387 not "b:current_compiler". What the command actually does is the following: | |
388 | |
389 - Delete the "current_compiler" and "b:current_compiler" variables. | |
390 - Define the "CompilerSet" user command. With "!" it does ":set", without "!" | |
391 it does ":setlocal". | |
392 - Execute ":runtime! compiler/{name}.vim". The plugins are expected to set | |
393 options with "CompilerSet" and set the "current_compiler" variable to the | |
394 name of the compiler. | |
395 - Delete the "CompilerSet user command. | |
396 - Set "b:current_compiler" to the value of "current_compiler". | |
397 - Without "!" the old value of "current_compiler" is restored. | |
398 | |
399 | |
400 For writing a compiler plugin, see |write-compiler-plugin|. | |
401 | |
402 | |
403 MANX AZTEC C *quickfix-manx* *compiler-manx* | |
404 | |
405 To use Vim with Manx's Aztec C compiler on the Amiga you should do the | |
406 following: | |
407 - Set the CCEDIT environment variable with the command: > | |
408 mset "CCEDIT=vim -q" | |
409 - Compile with the -qf option. If the compiler finds any errors, Vim is | |
410 started and the cursor is positioned on the first error. The error message | |
411 will be displayed on the last line. You can go to other errors with the | |
412 commands mentioned above. You can fix the errors and write the file(s). | |
413 - If you exit Vim normally the compiler will re-compile the same file. If you | |
414 exit with the :cq command, the compiler will terminate. Do this if you | |
415 cannot fix the error, or if another file needs to be compiled first. | |
416 | |
417 There are some restrictions to the Quickfix mode on the Amiga. The | |
418 compiler only writes the first 25 errors to the errorfile (Manx's | |
419 documentation does not say how to get more). If you want to find the others, | |
420 you will have to fix a few errors and exit the editor. After recompiling, | |
421 up to 25 remaining errors will be found. | |
422 | |
423 If Vim was started from the compiler, the :sh and some :! commands will not | |
424 work, because Vim is then running in the same process as the compiler and | |
425 stdin (standard input) will not be interactive. | |
426 | |
427 | |
428 PYUNIT COMPILER *compiler-pyunit* | |
429 | |
430 This is not actually a compiler, but a unit testing framework for the | |
431 Python language. It is included into standard Python distribution | |
432 starting from version 2.0. For older versions, you can get it from | |
433 http://pyunit.sourceforge.net. | |
434 | |
435 When you run your tests with the help of the framework, possible errors | |
436 are parsed by Vim and presented for you in quick-fix mode. | |
437 | |
438 Unfortunately, there is no standard way to run the tests. | |
439 The alltests.py script seems to be used quite often, that's all. | |
440 Useful values for the 'makeprg' options therefore are: | |
441 setlocal makeprg=./alltests.py " Run a testsuite | |
442 setlocal makeprg=python % " Run a single testcase | |
443 | |
444 Also see http://vim.sourceforge.net/tip_view.php?tip_id=280. | |
445 | |
446 | |
447 TEX COMPILER *compiler-tex* | |
448 | |
449 Included in the distribution compiler for TeX ($VIMRUNTIME/compiler/tex.vim) | |
450 uses make command if possible. If the compiler finds a file named "Makefile" | |
451 or "makefile" in the current directory, it supposes that you want to process | |
452 your *TeX files with make, and the makefile does the right work. In this case | |
453 compiler sets 'errorformat' for *TeX output and leaves 'makeprg' untouched. If | |
454 neither "Makefile" nor "makefile" is found, the compiler will not use make. | |
455 You can force the compiler to ignore makefiles by defining | |
456 b:tex_ignore_makefile or g:tex_ignore_makefile variable (they are checked for | |
457 existence only). | |
458 | |
459 If the compiler chose not to use make, it need to choose a right program for | |
460 processing your input. If b:tex_flavor or g:tex_flavor (in this precedence) | |
461 variable exists, it defines TeX flavor for :make (actually, this is the name | |
462 of executed command), and if both variables do not exist, it defaults to | |
463 "latex". For example, while editing chapter2.tex \input-ed from mypaper.tex | |
464 written in AMS-TeX: > | |
465 | |
466 :let b:tex_flavor = 'amstex' | |
467 :compiler tex | |
468 < [editing...] > | |
469 :make mypaper | |
470 | |
471 Note that you must specify a name of the file to process as an argument (to | |
472 process the right file when editing \input-ed or \include-ed file; portable | |
473 solution for substituting % for no arguments is welcome). This is not in the | |
474 semantics of make, where you specify a target, not source, but you may specify | |
475 filename without extension ".tex" and mean this as "make filename.dvi or | |
476 filename.pdf or filename.some_result_extension according to compiler". | |
477 | |
478 Note: tex command line syntax is set to usable both for MikTeX (suggestion | |
479 by Srinath Avadhanula) and teTeX (checked by Artem Chuprina). Suggestion | |
480 from |errorformat-LaTeX| is too complex to keep it working for different | |
481 shells and OSes and also does not allow to use other available TeX options, | |
482 if any. If your TeX doesn't support "-interaction=nonstopmode", please | |
483 report it with different means to express \nonstopmode from the command line. | |
484 | |
485 ============================================================================= | |
486 7. The error format *error-file-format* | |
487 | |
488 *errorformat* *E372* *E373* *E374* | |
489 *E375* *E376* *E377* *E378* | |
490 The 'errorformat' option specifies a list of formats that are recognized. The | |
491 first format that matches with an error message is used. You can add several | |
492 formats for different messages your compiler produces, or even entries for | |
493 multiple compilers. See |efm-entries|. | |
494 | |
495 Each entry in 'errorformat' is a scanf-like string that describes the format. | |
496 First, you need to know how scanf works. Look in the documentation of your | |
497 C compiler. Below you find the % items that Vim understands. Others are | |
498 invalid. | |
499 | |
500 Special characters in 'errorformat' are comma and backslash. See | |
501 |efm-entries| for how to deal with them. Note that a literal "%" is matched | |
502 by "%%", thus it is not escaped with a backslash. | |
503 | |
504 Note: By default the difference between upper and lowercase is ignored. If | |
505 you want to match case, add "\C" to the pattern |/\C|. | |
506 | |
507 | |
508 Basic items | |
509 | |
510 %f file name (finds a string) | |
511 %l line number (finds a number) | |
512 %c column number (finds a number representing character | |
513 column of the error, (1 <tab> == 1 character column)) | |
514 %v virtual column number (finds a number representing | |
515 screen column of the error (1 <tab> == 8 screen | |
516 columns) | |
517 %t error type (finds a single character) | |
518 %n error number (finds a number) | |
519 %m error message (finds a string) | |
520 %r matches the "rest" of a single-line file message %O/P/Q | |
521 %p pointer line (finds a sequence of '-', '.' or ' ' and | |
522 uses the length for the column number) | |
523 %*{conv} any scanf non-assignable conversion | |
524 %% the single '%' character | |
525 | |
526 The "%f" conversion depends on the current 'isfname' setting. | |
527 | |
528 The "%f" and "%m" conversions have to detect the end of the string. They | |
529 should be followed by a character that cannot be in the string. Everything | |
530 up to that character is included in the string. But when the next character | |
531 is a '%' or a backslash, "%f" will look for any 'isfname' character and "%m" | |
532 finds anything. If the "%f" or "%m" is at the end, everything up to the end | |
533 of the line is included. | |
534 | |
535 On MS-DOS, MS-Windows and OS/2 a leading "C:" will be included in "%f", even | |
536 when using "%f:". This means that a file name which is a single alphabetical | |
537 letter will not be detected. | |
538 | |
539 The "%p" conversion is normally followed by a "^". It's used for compilers | |
540 that output a line like: > | |
541 ^ | |
542 or > | |
543 ---------^ | |
544 to indicate the column of the error. This is to be used in a multi-line error | |
545 message. See |errorformat-javac| for a useful example. | |
546 | |
547 | |
548 Changing directory | |
549 | |
550 The following uppercase conversion characters specify the type of special | |
551 format strings. At most one of them may be given as a prefix at the begin | |
552 of a single comma-separated format pattern. | |
553 Some compilers produce messages that consist of directory names that have to | |
554 be prepended to each file name read by %f (example: GNU make). The following | |
555 codes can be used to scan these directory names; they will be stored in an | |
556 internal directory stack. *E379* | |
557 %D "enter directory" format string; expects a following | |
558 %f that finds the directory name | |
559 %X "leave directory" format string; expects following %f | |
560 | |
561 When defining an "enter directory" or "leave directory" format, the "%D" or | |
562 "%X" has to be given at the start of that substring. Vim tracks the directory | |
563 changes and prepends the current directory to each erroneous file found with a | |
564 relative path. See |quickfix-directory-stack| for details, tips and | |
565 limitations. | |
566 | |
567 | |
568 Multi-line messages *errorformat-multi-line* | |
569 | |
570 It is possible to read the output of programs that produce multi-line | |
571 messages, ie. error strings that consume more than one line. Possible | |
572 prefixes are: | |
573 %E start of a multi-line error message | |
574 %W start of a multi-line warning message | |
575 %I start of a multi-line informational message | |
576 %A start of a multi-line message (unspecified type) | |
577 %C continuation of a multi-line message | |
578 %Z end of a multi-line message | |
579 These can be used with '+' and '-', see |efm-ignore| below. | |
580 | |
581 Example: Your compiler happens to write out errors in the following format | |
582 (leading line numbers not being part of the actual output): | |
583 | |
584 1 Error 275 | |
585 2 line 42 | |
586 3 column 3 | |
587 4 ' ' expected after '--' | |
588 | |
589 The appropriate error format string has to look like this: > | |
590 :set efm=%EError\ %n,%Cline\ %l,%Ccolumn\ %c,%Z%m | |
591 | |
592 And the |:clist| error message generated for this error is: | |
593 | |
594 1:42 col 3 error 275: ' ' expected after '--' | |
595 | |
596 Another example: Think of a Python interpreter that produces the following | |
597 error message (line numbers are not part of the actual output): | |
598 | |
599 1 ============================================================== | |
600 2 FAIL: testGetTypeIdCachesResult (dbfacadeTest.DjsDBFacadeTest) | |
601 3 -------------------------------------------------------------- | |
602 4 Traceback (most recent call last): | |
603 5 File "unittests/dbfacadeTest.py", line 89, in testFoo | |
604 6 self.assertEquals(34, dtid) | |
605 7 File "/usr/lib/python2.2/unittest.py", line 286, in | |
606 8 failUnlessEqual | |
607 9 raise self.failureException, \ | |
608 10 AssertionError: 34 != 33 | |
609 11 | |
610 12 -------------------------------------------------------------- | |
611 13 Ran 27 tests in 0.063s | |
612 | |
613 Say you want |:clist| write the relevant information of this message only, | |
614 namely: | |
615 5 unittests/dbfacadeTest.py:89: AssertionError: 34 != 33 | |
616 | |
617 Then the error format string could be defined as follows: > | |
618 :set efm=%C\ %.%#,%A\ \ File\ \"%f\"\\,\ line\ %l%.%#,%Z%[%^\ ]%\\@=%m | |
619 | |
620 Note that the %C string is given before the %A here: since the expression | |
621 ' %.%#' (which stands for the regular expression ' .*') matches every line | |
622 starting with a space, followed by any characters to the end of the line, | |
623 it also hides line 7 which would trigger a separate error message otherwise. | |
624 Error format strings are always parsed pattern by pattern until the first | |
625 match occurs. | |
626 | |
627 | |
628 Separate file name *errorformat-separate-filename* | |
629 | |
630 These prefixes are useful if the file name is given once and multiple messages | |
631 follow that refer to this file name. | |
632 %O single-line file message: overread the matched part | |
633 %P single-line file message: push file %f onto the stack | |
634 %Q single-line file message: pop the last file from stack | |
635 | |
636 Example: Given a compiler that produces the following error logfile (without | |
637 leading line numbers): | |
638 | |
639 1 [a1.tt] | |
640 2 (1,17) error: ';' missing | |
641 3 (21,2) warning: variable 'z' not defined | |
642 4 (67,3) error: end of file found before string ended | |
643 5 | |
644 6 [a2.tt] | |
645 7 | |
646 8 [a3.tt] | |
647 9 NEW compiler v1.1 | |
648 10 (2,2) warning: variable 'x' not defined | |
649 11 (67,3) warning: 's' already defined | |
650 | |
651 This logfile lists several messages for each file enclosed in [...] which are | |
652 properly parsed by an error format like this: > | |
653 :set efm=%+P[%f],(%l\\,%c)%*[\ ]%t%*[^:]:\ %m,%-Q | |
654 | |
655 A call of |:clist| writes them accordingly with their correct filenames: | |
656 | |
657 2 a1.tt:1 col 17 error: ';' missing | |
658 3 a1.tt:21 col 2 warning: variable 'z' not defined | |
659 4 a1.tt:67 col 3 error: end of file found before string ended | |
660 8 a3.tt:2 col 2 warning: variable 'x' not defined | |
661 9 a3.tt:67 col 3 warning: 's' already defined | |
662 | |
663 Unlike the other prefixes that all match against whole lines, %P, %Q and %O | |
664 can be used to match several patterns in the same line. Thus it is possible | |
665 to parse even nested files like in the following line: | |
666 {"file1" {"file2" error1} error2 {"file3" error3 {"file4" error4 error5}}} | |
667 The %O then parses over strings that do not contain any push/pop file name | |
668 information. See |errorformat-LaTeX| for an extended example. | |
669 | |
670 | |
671 Ignoring and using whole messages *efm-ignore* | |
672 | |
673 The codes '+' or '-' can be combined with the uppercase codes above; in that | |
674 case they have to precede the letter, eg. '%+A' or '%-G': | |
675 %- do not include the matching multi-line in any output | |
676 %+ include the whole matching line in the %m error string | |
677 | |
678 One prefix is only useful in combination with '+' or '-', namely %G. It parses | |
679 over lines containing general information like compiler version strings or | |
680 other headers that can be skipped. | |
681 %-G ignore this message | |
682 %+G general message | |
683 | |
684 | |
685 Pattern matching | |
686 | |
687 The scanf()-like "%*[]" notation is supported for backward-compatibility | |
688 with previous versions of Vim. However, it is also possible to specify | |
689 (nearly) any Vim supported regular expression in format strings. | |
690 Since meta characters of the regular expression language can be part of | |
691 ordinary matching strings or file names (and therefore internally have to | |
692 be escaped), meta symbols have to be written with leading '%': | |
693 %\ the single '\' character. Note that this has to be | |
694 escaped ("%\\") in ":set errorformat=" definitions. | |
695 %. the single '.' character. | |
696 %# the single '*'(!) character. | |
697 %^ the single '^' character. | |
698 %$ the single '$' character. | |
699 %[ the single '[' character for a [] character range. | |
700 %~ the single '~' character. | |
701 When using character classes in expressions (see |/\i| for an overview), | |
702 terms containing the "\+" quantifier can be written in the scanf() "%*" | |
703 notation. Example: "%\\d%\\+" ("\d\+", "any number") is equivalent to "%*\\d". | |
704 Important note: The \(...\) grouping of sub-matches can not be used in format | |
705 specifications because it is reserved for internal conversions. | |
706 | |
707 | |
708 Multiple entries in 'errorformat' *efm-entries* | |
709 | |
710 To be able to detect output from several compilers, several format patterns | |
711 may be put in 'errorformat', separated by commas (note: blanks after the comma | |
712 are ignored). The first pattern that has a complete match is used. If no | |
713 match is found, matching parts from the last one will be used, although the | |
714 file name is removed and the error message is set to the whole message. If | |
715 there is a pattern that may match output from several compilers (but not in a | |
716 right way), put it after one that is more restrictive. | |
717 | |
718 To include a comma in a pattern precede it with a backslash (you have to type | |
719 two in a ":set" command). To include a backslash itself give two backslashes | |
720 (you have to type four in a ":set" command). You also need to put a backslash | |
721 before a space for ":set". | |
722 | |
723 | |
724 Valid matches *quickfix-valid* | |
725 | |
726 If a line does not completely match one of the entries in 'errorformat', the | |
727 whole line is put in the error message and the entry is marked "not valid" | |
728 These lines are skipped with the ":cn" and ":cp" commands (unless there is | |
729 no valid line at all). You can use ":cl!" to display all the error messages. | |
730 | |
731 If the error format does not contain a file name Vim cannot switch to the | |
732 correct file. You will have to do this by hand. | |
733 | |
734 | |
735 Examples | |
736 | |
737 The format of the file from the Amiga Aztec compiler is: | |
738 | |
739 filename>linenumber:columnnumber:errortype:errornumber:errormessage | |
740 | |
741 filename name of the file in which the error was detected | |
742 linenumber line number where the error was detected | |
743 columnnumber column number where the error was detected | |
744 errortype type of the error, normally a single 'E' or 'W' | |
745 errornumber number of the error (for lookup in the manual) | |
746 errormessage description of the error | |
747 | |
748 This can be matched with this 'errorformat' entry: | |
749 %f>%l:%c:%t:%n:%m | |
750 | |
751 Some examples for C compilers that produce single-line error outputs: | |
752 %f:%l:\ %t%*[^0123456789]%n:\ %m for Manx/Aztec C error messages | |
753 (scanf() doesn't understand [0-9]) | |
754 %f\ %l\ %t%*[^0-9]%n:\ %m for SAS C | |
755 \"%f\"\\,%*[^0-9]%l:\ %m for generic C compilers | |
756 %f:%l:\ %m for GCC | |
757 %f:%l:\ %m,%Dgmake[%*\\d]:\ Entering\ directory\ `%f', | |
758 %Dgmake[%*\\d]:\ Leaving\ directory\ `%f' | |
759 for GCC with gmake (concat the lines!) | |
760 %f(%l)\ :\ %*[^:]:\ %m old SCO C compiler (pre-OS5) | |
761 %f(%l)\ :\ %t%*[^0-9]%n:\ %m idem, with error type and number | |
762 %f:%l:\ %m,In\ file\ included\ from\ %f:%l:,\^I\^Ifrom\ %f:%l%m | |
763 for GCC, with some extras | |
764 | |
765 Extended examples for the handling of multi-line messages are given below, | |
766 see |errorformat-Jikes| and |errorformat-LaTeX|. | |
767 | |
768 Note the backslash in front of a space and double quote. It is required for | |
769 the :set command. There are two backslashes in front of a comma, one for the | |
770 :set command and one to avoid recognizing the comma as a separator of error | |
771 formats. | |
772 | |
773 | |
774 Filtering messages | |
775 | |
776 If you have a compiler that produces error messages that do not fit in the | |
777 format string, you could write a program that translates the error messages | |
778 into this format. You can use this program with the ":make" command by | |
779 changing the 'makeprg' option. For example: > | |
780 :set mp=make\ \\\|&\ error_filter | |
781 The backslashes before the pipe character are required to avoid it to be | |
782 recognized as a command separator. The backslash before each space is | |
783 required for the set command. | |
784 | |
785 ============================================================================= | |
786 8. The directory stack *quickfix-directory-stack* | |
787 | |
788 Quickfix maintains a stack for saving all used directories parsed from the | |
789 make output. For GNU-make this is rather simple, as it always prints the | |
790 absolute path of all directories it enters and leaves. Regardless if this is | |
791 done via a 'cd' command in the makefile or with the parameter "-C dir" (change | |
792 to directory before reading the makefile). It may be useful to use the switch | |
793 "-w" to force GNU-make to print out the working directory before and after | |
794 processing. | |
795 | |
796 Maintaining the correct directory is more complicated if you don't use | |
797 GNU-make. AIX-make for example doesn't print any information about its working | |
798 directory. Then you need to enhance the makefile. In the makefile of lesstiff | |
799 there is a command which echoes "Making {target} in {dir}". The special | |
800 problem here is that it doesn't print informations on leaving the directory | |
801 and that it doesn't print the absolute path. | |
802 | |
803 To solve the problem with relative paths and missing "leave directory" | |
804 messages Vim uses following algorithm: | |
805 | |
806 1) Check if the given directory is a subdirectory of the current directory. | |
807 If this is true, store it as the current directory. | |
808 2) If it is not a subdir of the current directory, try if this is a | |
809 subdirectory of one of the upper directories. | |
810 3) If the directory still isn't found, it is assumed to be a subdirectory | |
811 of Vim's current directory. | |
812 | |
813 Additionally it is checked for every file, if it really exists in the | |
814 identified directory. If not, it is searched in all other directories of the | |
815 directory stack (NOT the directory subtree!). If it is still not found, it is | |
816 assumed that it is in Vim's current directory. | |
817 | |
818 There are limitation in this algorithm. This examples assume that make just | |
819 prints information about entering a directory in the form "Making all in dir". | |
820 | |
821 1) Assume you have following directories and files: | |
822 ./dir1 | |
823 ./dir1/file1.c | |
824 ./file1.c | |
825 | |
826 If make processes the directory "./dir1" before the current directory and | |
827 there is an error in the file "./file1.c", you will end up with the file | |
828 "./dir1/file.c" loaded by Vim. | |
829 | |
830 This can only be solved with a "leave directory" message. | |
831 | |
832 2) Assume you have following directories and files: | |
833 ./dir1 | |
834 ./dir1/dir2 | |
835 ./dir2 | |
836 | |
837 You get the following: | |
838 | |
839 Make output Directory interpreted by Vim | |
840 ------------------------ ---------------------------- | |
841 Making all in dir1 ./dir1 | |
842 Making all in dir2 ./dir1/dir2 | |
843 Making all in dir2 ./dir1/dir2 | |
844 | |
845 This can be solved by printing absolute directories in the "enter directory" | |
846 message or by printing "leave directory" messages.. | |
847 | |
848 To avoid this problems, ensure to print absolute directory names and "leave | |
849 directory" messages. | |
850 | |
851 Examples for Makefiles: | |
852 | |
853 Unix: | |
854 libs: | |
855 for dn in $(LIBDIRS); do \ | |
856 (cd $$dn; echo "Entering dir '$$(pwd)'"; make); \ | |
857 echo "Leaving dir"; \ | |
858 done | |
859 | |
860 Add | |
861 %DEntering\ dir\ '%f',%XLeaving\ dir | |
862 to your 'errorformat' to handle the above output. | |
863 | |
864 Note that Vim doesn't check if the directory name in a "leave directory" | |
865 messages is the current directory. This is why you could just use the message | |
866 "Leaving dir". | |
867 | |
868 ============================================================================= | |
869 9. Specific error file formats *errorformats* | |
870 | |
871 *errorformat-Jikes* | |
872 Jikes(TM), a source-to-bytecode Java compiler published by IBM Research, | |
873 produces simple multi-line error messages. | |
874 | |
875 An 'errorformat' string matching the produced messages is shown below. | |
876 The following lines can be placed in the user's |vimrc| to overwrite Vim's | |
877 recognized default formats, or see |:set+=| how to install this format | |
878 additionally to the default. > | |
879 | |
880 :set efm=%A%f:%l:%c:%*\\d:%*\\d:, | |
881 \%C%*\\s%trror:%m, | |
882 \%+C%*[^:]%trror:%m, | |
883 \%C%*\\s%tarning:%m, | |
884 \%C%m | |
885 < | |
886 Jikes(TM) produces a single-line error message when invoked with the option | |
887 "+E", and can be matched with the following: > | |
888 | |
889 :set efm=%f:%l:%v:%*\\d:%*\\d:%*\\s%m | |
890 < | |
891 *errorformat-javac* | |
892 This 'errorformat' has been reported to work well for javac, which outputs a | |
893 line with "^" to indicate the column of the error: > | |
894 :set efm=%A%f:%l:\ %m,%-Z%p^,%-C%.%# | |
895 or: > | |
896 :set efm=%A%f:%l:\ %m,%+Z%p^,%+C%.%#,%-G%.%# | |
897 < | |
898 *errorformat-ant* | |
899 For ant (http://jakarta.apache.org/) the above errorformat has to be modified | |
900 to honour the leading [javac] in front of each javac output line: > | |
901 :set efm=%A\ %#[javac]\ %f:%l:\ %m,%-Z\ %#[javac]\ %p^,%-C%.%# | |
902 | |
903 The 'errorformat' can also be configured to handle ant together with either | |
904 javac or jikes. If you're using jikes, you should tell ant to use jikes' +E | |
905 command line switch which forces jikes to generate one-line error messages. | |
906 This is what the second line (of a build.xml file) below does: > | |
907 <property name = "build.compiler" value = "jikes"/> | |
908 <property name = "build.compiler.emacs" value = "true"/> | |
909 | |
910 The 'errorformat' which handles ant with both javac and jikes is: > | |
911 :set efm=\ %#[javac]\ %#%f:%l:%c:%*\\d:%*\\d:\ %t%[%^:]%#:%m, | |
912 \%A\ %#[javac]\ %f:%l:\ %m,%-Z\ %#[javac]\ %p^,%-C%.%# | |
913 < | |
914 *errorformat-jade* | |
915 parsing jade (see http://www.jclark.com/) errors is simple: > | |
916 :set efm=jade:%f:%l:%c:%t:%m | |
917 < | |
918 *errorformat-LaTeX* | |
919 The following is an example how an 'errorformat' string can be specified | |
920 for the (La)TeX typesetting system which displays error messages over | |
921 multiple lines. The output of ":clist" and ":cc" etc. commands displays | |
922 multi-lines in a single line, leading white space is removed. | |
923 It should be easy to adopt the above LaTeX errorformat to any compiler output | |
924 consisting of multi-line errors. | |
925 | |
926 The commands can be placed in a |vimrc| file or some other Vim script file, | |
927 eg. a script containing LaTeX related stuff which is loaded only when editing | |
928 LaTeX sources. | |
929 Make sure to copy all lines of the example (in the given order), afterwards | |
930 remove the comment lines. For the '\' notation at the start of some lines see | |
931 |line-continuation|. | |
932 | |
933 First prepare 'makeprg' such that LaTeX will report multiple | |
934 errors; do not stop when the first error has occurred: > | |
935 :set makeprg=latex\ \\\\nonstopmode\ \\\\input\\{$*} | |
936 < | |
937 Start of multi-line error messages: > | |
938 :set efm=%E!\ LaTeX\ %trror:\ %m, | |
939 \%E!\ %m, | |
940 < Start of multi-line warning messages; the first two also | |
941 include the line number. Meaning of some regular expressions: | |
942 - "%.%#" (".*") matches a (possibly empty) string | |
943 - "%*\\d" ("\d\+") matches a number > | |
944 \%+WLaTeX\ %.%#Warning:\ %.%#line\ %l%.%#, | |
945 \%+W%.%#\ at\ lines\ %l--%*\\d, | |
946 \%WLaTeX\ %.%#Warning:\ %m, | |
947 < Possible continuations of error/warning messages; the first | |
948 one also includes the line number: > | |
949 \%Cl.%l\ %m, | |
950 \%+C\ \ %m., | |
951 \%+C%.%#-%.%#, | |
952 \%+C%.%#[]%.%#, | |
953 \%+C[]%.%#, | |
954 \%+C%.%#%[{}\\]%.%#, | |
955 \%+C<%.%#>%.%#, | |
956 \%C\ \ %m, | |
957 < Lines that match the following patterns do not contain any | |
958 important information; do not include them in messages: > | |
959 \%-GSee\ the\ LaTeX%m, | |
960 \%-GType\ \ H\ <return>%m, | |
961 \%-G\ ...%.%#, | |
962 \%-G%.%#\ (C)\ %.%#, | |
963 \%-G(see\ the\ transcript%.%#), | |
964 < Generally exclude any empty or whitespace-only line from | |
965 being displayed: > | |
966 \%-G\\s%#, | |
967 < The LaTeX output log does not specify the names of erroneous | |
968 source files per line; rather they are given globally, | |
969 enclosed in parentheses. | |
970 The following patterns try to match these names and store | |
971 them in an internal stack. The patterns possibly scan over | |
972 the same input line (one after another), the trailing "%r" | |
973 conversion indicates the "rest" of the line that will be | |
974 parsed in the next go until the end of line is reached. | |
975 | |
976 Overread a file name enclosed in '('...')'; do not push it | |
977 on a stack since the file apparently does not contain any | |
978 error: > | |
979 \%+O(%f)%r, | |
980 < Push a file name onto the stack. The name is given after '(': > | |
981 \%+P(%f%r, | |
982 \%+P\ %\\=(%f%r, | |
983 \%+P%*[^()](%f%r, | |
984 \%+P[%\\d%[^()]%#(%f%r, | |
985 < Pop the last stored file name when a ')' is scanned: > | |
986 \%+Q)%r, | |
987 \%+Q%*[^()])%r, | |
988 \%+Q[%\\d%*[^()])%r | |
989 | |
990 Note that in some cases file names in the LaTeX output log cannot be parsed | |
991 properly. The parser might have been messed up by unbalanced parentheses | |
992 then. The above example tries to catch the most relevant cases only. | |
993 You can customize the given setting to suit your own purposes, for example, | |
994 all the annoying "Overfull ..." warnings could be excluded from being | |
995 recognized as an error. | |
996 Alternatively to filtering the LaTeX compiler output, it is also possible | |
997 to directly read the *.log file that is produced by the [La]TeX compiler. | |
998 This contains even more useful information about possible error causes. | |
999 However, to properly parse such a complex file, an external filter should | |
1000 be used. See the description further above how to make such a filter known | |
1001 by Vim. | |
1002 | |
1003 *errorformat-Perl* | |
1004 In $VIMRUNTIME/tools you can find the efm_perl.pl script, which filters Perl | |
1005 error messages into a format that quickfix mode will understand. See the | |
1006 start of the file about how to use it. | |
1007 | |
1008 | |
1009 | |
1010 vim:tw=78:ts=8:ft=help:norl: |