On 2011-01-04, SungHyun Nam wrote:
> Gary Johnson wrote:
> >On 2011-01-04, SungHyun Nam wrote:
> >>Ben Fritz wrote:
> >>>
> >>>On Jan 2, 7:01 pm, SungHyun Nam<[email protected]> wrote:
> >>>>Hello,
> >>>>
> >>>>There is always a message:
> >>>>
> >>>> CTIME - 2011-01-03 09:57:57
> >>>>
> >>>>And vim detects it as error message.
> >>>>
> >>>>Can vim ignore this message? starting with CTIME...
> >>>>Or ignore a message if it cannot find a file in message.
> >>>
> >>>Which compiler is this? Are you using the correct errorformat for that
> >>>compiler or just the default errorformat?
> >>
> >>It is not a compiler's output, but a message from a tool which
> >>called by makefile. So that, I wanted to ignore this message by
> >>tweaking the 'errorformat' without success. :(
> >>
> >>And I use default errorformat. Just tried to tweak default
> >>errorformat to ignore that message.
> >>
> >>I can use filter like:
> >> tool ... | sed 's/\([0-9]*\):\([0-9]*\):\([0-9]*\)/\1.\2.\3/g'
> >>(Not good, I think.)
> >>
> >>Actually I wanted to raise a issue like:
> >> can VIM ignore errorformat if a file is not found?
> >>
> >>Also, in the hope someone suggest a 'errorformat' which ignore
> >>that message.
> >
> >You can add a pattern to the end of your 'errorformat' option like
> >this:
> >
> > setlocal errorformat+=%-G%.%#
> >
> >That will cause Vim to ignore any pattern not yet matched. See
> >
> > :help efm-ignore
>
> It does not work. You can check with the sequence below:
>
> $ cat m.sh
> #!/bin/bash
> echo 'CTIME - 2000-01-01 12:34:56'
> exit 0
>
> $ vim
> :set errorformat+=%-G%.%# makeprg=./m.sh
> :make
>
> Now, vim opens 'CTIME - 2000-01-01 12' file.
I see now that I misunderstood the problem. Thank you for the
example. In that case, a solution would be to put a pattern
matching the CTIME line at the front of 'errorformat', like so:
set errorformat^=%-GCTIME\ -\ %.%#
Note the ^= operator and that spaces in the pattern are escaped with
backslashes. See
:help set^=
Whether you use "set" or "setlocal" depends on what you wish the
scope of the resulting 'errorformat' to be.
Regards,
Gary
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
