On Thursday, November 12, 2015 at 2:15:06 PM UTC-5, Ben Fritz wrote:
> On Thursday, November 12, 2015 at 1:06:34 PM UTC-6, Borges, Matt wrote:
> > I’m trying to use efm in vim with multiple compilers each of which use 
> > multi-line error messages.  The problem I am having is that only the first 
> > error shows up in the quick fix window.  However, if change efm to only 
> > have the error format for the compiler
> >  currently being used, I see all the errors.  Here’s an example:
> 
> Do you have a reason that you need all the compiler settings combined into 
> one error format? For example, does your make process run multiple different 
> compilers in one build, or do you concatenate all your compiles into one log 
> to use with :cfile?
> 
> If not, then you probably are better off only ever setting the errorformat 
> for the compiler you're using. I think that's the intended operation.
> 
> In fact, Vim provides the capability to write a "compiler plugin" (:help 
> write-compiler-plugin) to set up errorformat, makeprg, etc. for a single 
> compiler using one :compiler command. That's probably what you ought to be 
> using.
> 
> In fact, there is already a javac compiler plugin distributed with Vim. Try 
> it out with ":compiler javac" or take a look at it's settings in 
> $VIMRUNTIME/compiler/javac.vim. I don't see a clang compiler plugin, however.

It is possible that one call to the make process will result in several 
compilers being used.

>From reading the vim help I was under the impression that it is possible to 
>setup errorformat so that it can match output from multiple compilers.  If 
>that is not possible, I can change my setup.

Thanks,
Matt

-- 
-- 
You received this message from the "vim_use" 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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to