ccfilter.1   [plain text]

.TH ccfilter 1 "01-Apr-97"
ccfilter \- a compiler's output filter for vim quickfix
ccfilter [
.B <options>
The ccfilter utility "filters" the output of several compilers
and makers (make/gmake) from several platforms (see NOTES below)
to a standardized format which easily fits in vim's quickfix
feature. For further details, see in vim ":help quickfix".
ccfilter reads
.B 'stdin'
and outputs to
.B 'stdout'
The need for ccfilter is clear, as some compilers have irregular
and/or multiple line error messages (with the relevant information on
line 2), which makes it impossible for the errorformat to correctly
display them !

When working on different platforms, and with different compilers,
ccfilter eases the utilization of quickfix, due to it's standardized
output, allowing to have in .vimrc a plain
.B \ \ \ \ :set\ errorformat=%f:%l:%c:%t:%m

When using ccfilter, one would include the following lines in .vimrc:
.B \ \ \ \ :set shellpipe=\\\\|&ccfilter\\\\>
.B \ \ \ \ :set errorformat=%f:%l:%c:%t:%m

.TP 16
Decrement column by one. This may be needed, depending on
the compiler being used.
Decrement row by one.  This may be needed, depending on
the compiler being used.
Verbose (Outputs also invalid lines).
This option makes ccfilter output also the lines that
couldn't be correctly parsed. This is used mostly for
ccfilter debugging.
Treat input as <COMPILER>'s output.
Even when configuring ccfilter to assume a default
COMPILER, sometimes it's helpful to be able to specify
the COMPILER used to generate ccfilter's input.
For example, when cross-compiling on a network from a
single machine.
Shows a brief help, describing the configured default COMPILER
and the valid parameters for COMPILER.

Currently, ccfilter accepts output from several compilers, as
described below:
.TP 10
GCC compiler
AIX's C compiler
AT&T/NCR's High Performance C Compiler
IRIX's MIPS/MIPSpro C compiler
SOLARIS's SparcWorks C compiler
HPUX's C compiler

.B ccfilter
was developed by
.B Pablo Ariel Kohan