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