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