Hi --

[Please excuse me if you've already seen this; I posted this to
comp.editors before I found this list.]


After reading the docs many times and searching comp.editorsfor help, I
admit I'm stumped -- I simply don't know how to set errorformat properly
to recognize my messages. Here's what I've got:

1.  Error/Warning/Information messages may be either one or several
    lines.

2.  There may be zero, one or more locations in the code pointed to
    by a message; but no more than one location per line in a multiline
    message.

3.  Locations are (literally; including brackets): [filename:line:column]

Sample output is:

    Warning [flip.jss:7:10]: type mismatch:
        conflict between boolean [flip.jss:4:19]
        and string [flip.jss:7:10]
    Warning [flip.jss:18:5]: different argument counts:
        conflict between 2 arguments [flip.jss:18:9]
        and 1 argument [flip.jss:3:14]
    Warning [flip.jss:20:7]: invalid "+" usage:
        boolean [flip.jss:4:16]
        + undetermined type [flip.jss:20:9]
        = undetermined type

The simplest way (for me) to treat these is that each line is a
separate message, with an error location within brackets. So, the
errorformat should specify:

    - any non-'[' characters
    - a '['
    - the filename
    - a ':'
    - the linenumber
    - a ':'
    - the column
    - a ']'
    - the message

which I think means:

    set errorformat=%[^[][%f:%l:%v]%m

However, in the quickfix window (:copen), the only lines that are
handled as messages are those with "Warning"; others are unrecognized.
The quickfix window looks like:

    flip.jss|7 col 10| : type mismatch:
    ||     conflict between boolean [flip.jss:4:19]
    ||     and string [flip.jss:7:10]
    flip.jss|18 col 5| : different argument counts:
    ||     conflict between 2 arguments [flip.jss:18:9]
    ||     and 1 argument [flip.jss:3:14]
    flip.jss|20 col 7| : invalid "+" usage:
    ||     boolean [flip.jss:4:16]
    ||     + undetermined type [flip.jss:20:9]
    ||     = undetermined type

I said aha! and rewrote the error messages without leading spaces.
This had no effect, though ... the lines unlabeled with "Warning"
still were not recognized.

I've tried a lot of other errorformat values, none of which work any
better (most are worse). At this point I feel like I'm reduced to trying
to find a working "magical incantation", rather than understanding and
applying a proper errorformat syntax.

I would *really* appreciate any help. Thanks!


Howard
[EMAIL PROTECTED]

Reply via email to