Lines Matching refs:messages

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
411 When 'encoding' differs from the locale, the error messages may have a
412 different encoding from what Vim is using.  To convert the messages you can
959 It may be that 'encoding' is set to an encoding that differs from the messages
961 read the error messages: >
1362 formats for different messages your compiler produces, or even entries for
1446 Some compilers produce messages that consist of directory names that have to
1461 Multi-line messages				*errorformat-multi-line*
1464 messages, i.e. error strings that consume more than one line.  Possible
1476 Using "\n" in the pattern won't work to match multi-line messages.
1548 These prefixes are useful if the file name is given once and multiple messages
1569 This logfile lists several messages for each file enclosed in [...] which are
1589 Ignoring and using whole messages			*efm-ignore*
1649 no valid line at all).  You can use ":cl!" to display all the error messages.
1672 %f:%l:\ %t%*[^0123456789]%n:\ %m	for Manx/Aztec C error messages
1685 Extended examples for the handling of multi-line messages are given below,
1694 Filtering messages
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
1724 messages Vim uses the following algorithm:
1766    message or by printing "leave directory" messages.
1769 directory" messages.
1785 messages is the current directory.  This is why you could just use the message
1793 produces simple multi-line error messages.
1795 An 'errorformat' string matching the produced messages is shown below.
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
1874 		Start of multi-line error messages: >
1877 <		Start of multi-line warning messages; the first two also
1884 <		Possible continuations of error/warning messages; the first
1895 		important information; do not include them in messages: >
1942 error messages into a format that quickfix mode will understand.  See the