Lines Matching refs:error
10 2. The error window |quickfix-window|
11 3. Using more than one list of errors |quickfix-error-lists|
15 7. The error format |error-file-format|
17 9. Specific error file formats |errorformats|
28 The idea is to save the error messages from the compiler in a file and use Vim
30 without having to remember all the error messages.
37 If you have the error messages in a file you can start Vim with: >
43 The 'errorformat' option should be set to match the error messages from your
88 :cc[!] [nr] Display error [nr]. If [nr] is omitted, the same
89 :[nr]cc[!] error is displayed again. Without [!] this doesn't
107 :[count]cn[ext][!] Display the [count] next error in the list that
109 all, go to the [count] next error. See |:cc| for
117 :[count]cp[revious][!] Display the [count] previous error in the list that
119 all, go to the [count] previous error. See |:cc| for
129 :[count]cabo[ve] Go to the [count] error above the current line in the
131 used. If there are no errors, then an error message
137 first error in the file is selected.
144 :[count]cbel[ow] Go to the [count] error below the current line in the
146 used. If there are no errors, then an error message
152 then the last error in the file is selected.
159 :[count]cbe[fore] Go to the [count] error before the current cursor
162 an error message is displayed. Assumes that the
166 the first error in the file is selected.
173 :[count]caf[ter] Go to the [count] error after the current cursor
176 an error message is displayed. Assumes that the
180 the last error in the file is selected.
187 :[count]cnf[ile][!] Display the first error in the [count] next file in
190 the [count] next error. See |:cc| for [!] and
198 :[count]cpf[ile][!] Display the last error in the [count] previous file in
201 the [count] previous error. See |:cc| for [!] and
211 :cr[ewind][!] [nr] Display error [nr]. If [nr] is omitted, the FIRST
212 error is displayed. See |:cc|.
225 :cla[st][!] [nr] Display error [nr]. If [nr] is omitted, the LAST
226 error is displayed. See |:cc|.
235 :cq[uit][!] {N} Quit Vim with error code {N}. {N} defaults to one.
248 :cf[ile][!] [errorfile] Read the error file and jump to the first error.
254 If the encoding of the error file differs from the
266 Read the error file. Just like ":cfile" but don't
267 jump to the first error.
268 If the encoding of the error file differs from the
278 :caddf[ile] [errorfile] Read the error file and add the errors from the
281 If the encoding of the error file differs from the
290 :cb[uffer][!] [bufnr] Read the error list from the current buffer.
303 :cgetb[uffer] [bufnr] Read the error list from the current buffer. Just
304 like ":cbuffer" but don't jump to the first error.
312 :cad[dbuffer] [bufnr] Read the error list from the current buffer and add
324 jump to the first error.
343 Just like |:cexpr|, but don't jump to the first error.
367 from the last error backwards, -1 being the last error.
377 is the current error position.
382 :cl[ist]! +{count} List the current and next {count} error lines. This
385 8384 testje.java:252: error: cannot find symbol ~
387 8384 testje.java:252: error: cannot find symbol ~
400 If you insert or delete lines, mostly the correct error location is still
403 the error location may not be correct. If you quit Vim and start again the
404 marks are lost and the error locations may not be correct anymore.
411 When 'encoding' differs from the locale, the error messages may have a
499 The last buffer (or where an error occurred) becomes
572 2. The error window *quickfix-window*
645 In the quickfix window, each line is one error. The line number is equal to
646 the error number. The current entry is highlighted with the QuickFixLine
650 You can use ":.cc" to jump to the error under the cursor.
652 effect. The file containing the error is opened in the window above the
654 instead. If the buffer in the used window has changed, and the error is in
655 another file, jumping to the error will fail. You will first have to make
658 You can use CTRL-W <Enter> to open a new window and jump to the error there.
679 lines anyway, the relation between the text and the error number is messed up.
681 window to a file and use ":cfile" to have it parsed and used as the new error
831 3. Using more than one list of errors *quickfix-error-lists*
835 ones are automatically kept. Two commands can be used to access older error
836 lists. They set one of the existing error lists as the current one.
839 :col[der] [count] Go to older error list. When [count] is given, do
840 this [count] times. When already at the oldest error
841 list, an error message is given.
848 :cnew[er] [count] Go to newer error list. When [count] is given, do
849 this [count] times. When already at the newest error
850 list, an error message is given.
857 :[count]chi[story] Show the list of error lists. The current list is
859 error list 1 of 3; 43 errors ~
860 > error list 2 of 3; 0 errors ~
861 error list 3 of 3; 15 errors ~
872 When adding a new error list, it becomes the current list.
874 When ":colder" has been used and ":make" or ":grep" is used to add a new error
876 browsing with ":grep" |grep|. If you want to keep the more recent error
906 7. If [!] is not given the first error is jumped to.
961 read the error messages: >
1013 the error list to the matches. Files matching
1058 :vimgrep /an error/ *.c
1119 < The first command makes a new error list which is
1122 ":grepadd" jumps to the first error, which is not
1168 error in |quickfix| mode. You can then use the |:cnext|, |:clist|, etc.
1188 Using the stack of error lists that Vim keeps, you can browse your files to
1268 started and the cursor is positioned on the first error. The error message
1273 cannot fix the error, or if another file needs to be compiled first.
1356 7. The error format *error-file-format*
1361 first format that matches with an error message is used. You can add several
1389 column of the error, byte index, a <tab> is 1
1392 screen column of the error (1 <tab> == 8 screen
1394 %t error type (finds a single character):
1395 e - error message
1399 %n error number (finds a number)
1400 %m error message (finds a string)
1425 to indicate the column of the error. This is to be used in a multi-line error
1428 The "%s" conversion specifies the text to search for, to locate the error line.
1430 the text to locate the error line exactly matching the search text and the
1432 conversion can be used to locate lines without a line number in the error
1437 it will be used in quickfix error window instead of the filename. The module
1464 messages, i.e. error strings that consume more than one line. Possible
1466 %E start of a multi-line error message
1486 The appropriate error format string has to look like this: >
1489 And the |:clist| error message generated for this error is:
1491 1:42 col 3 error 275: ' ' expected after '--'
1494 error message (line numbers are not part of the actual output):
1514 Then the error format string could be defined as follows: >
1520 it also hides line 7 which would trigger a separate error message otherwise.
1526 For example, if the error looks like this:
1536 every line in the error file gets a complete new run through the error format
1539 Where aa, bb, etc. are error format strings. Each line of the error file will
1541 the previous error line does _not_ mean that dd will be tried first on the
1554 Example: Given a compiler that produces the following error logfile (without
1558 2 (1,17) error: ';' missing
1560 4 (67,3) error: end of file found before string ended
1570 properly parsed by an error format like this: >
1575 2 a1.tt:1 col 17 error: ';' missing
1577 4 a1.tt:67 col 3 error: end of file found before string ended
1594 %+ include the whole matching line in the %m error string
1634 file name is removed and the error message is set to the whole message. If
1647 whole line is put in the error message and the entry is marked "not valid"
1649 no valid line at all). You can use ":cl!" to display all the error messages.
1651 If the error format does not contain a file name Vim cannot switch to the
1661 filename name of the file in which the error was detected
1662 linenumber line number where the error was detected
1663 columnnumber column number where the error was detected
1664 errortype type of the error, normally a single 'E' or 'W'
1665 errornumber number of the error (for lookup in the manual)
1666 errormessage description of the error
1671 Some examples for C compilers that produce single-line error outputs:
1672 %f:%l:\ %t%*[^0123456789]%n:\ %m for Manx/Aztec C error messages
1681 %f(%l)\ :\ %t%*[^0-9]%n:\ %m idem, with error type and number
1690 :set command and one to avoid recognizing the comma as a separator of error
1696 If you have a compiler that produces error messages that do not fit in the
1697 format string, you could write a program that translates the error messages
1747 there is an error in the file "./file1.c", you will end up with the file
1789 9. Specific error file formats *errorformats*
1793 produces simple multi-line error messages.
1806 Jikes(TM) produces a single-line error message when invoked with the option
1813 line with "^" to indicate the column of the error: >
1830 - Moves the line with the filename, line number, error message to just after
1831 the pointer line. That way, the unused error text between doesn't break
1842 command line switch which forces jikes to generate one-line error messages.
1857 for the (La)TeX typesetting system which displays error messages over
1871 errors; do not stop when the first error has occurred: >
1874 Start of multi-line error messages: >
1884 < Possible continuations of error/warning messages; the first
1915 error: >
1932 recognized as an error.
1935 This contains even more useful information about possible error causes.
1942 error messages into a format that quickfix mode will understand. See the
1993 window. As there is no line, column number and error text information