Splint, Errorformat and Windows Paths

2007-04-12 Thread Keith Prickett
I am trying to get Splint output to be parsed by gVim errorformat.  I
have used the following error format with Splint 3.1.1 and Vim 7.0.152:

:set errorformat=%A%f(%l\\,%c):\ %m,%+C\ %.%#

This seems to work pretty well, except files with Windows (I'm using
gVim on Windows XP) paths are not recognized using %f (or the
errorformat is not quite right).  For example foobar.c(line,column):
error message IS recognized and the error is shown using :cn and :cp.
The line containing C:\foo\bar\foobar.h(line,colum): error message is
NOT recognized.

Has anyone had any experience in this area or can anyone lend some
insight?



Second question: Can I save the current makeprg, change the makeprg to
splint, run make, then change the makeprg back using a vim function?
I've seen the local errorformat used which helps with the errorformat,
but I haven't seen a local makeprg.



Thanks,

--
Keith Prickett



Quickfix and regular expressions

2006-10-06 Thread Keith Prickett
When attempting to find errors and warnings using vim's make or
quickfix I am bogged down by a warning that I don't want to see.  The
warning I don't want to see is in this format:

../../buildrules.mk:77: file.d: No such file or directory

A warning or error I DO WANT to see might look like this:


filename.c:566: warning: implicit declaration of function
`function_name'

or other warnings or errors.


I am attempting to create a regular expression/matching pattern that
will capture errors and warnings in the above format (an error won't
have the warning: text, just a message after the filename and line
number).

My current efm includes %f:%l:\ %m as the matching pattern which
matches all wanted errors and warnings but also captures the .d: no
such file warning above.

--
Does anyone know a good regular expression for quickfix that will help
me sift through the weeds?




Using: GVIM7.0 and Windows.


Thank you,
--
Keith A. Prickett
Marvell Semiconductor, Inc.