Loading ...
Sorry, an error occurred while loading the content.

Re: Why I always get some automatic garbage buffer?

Expand Messages
  • Steven Woody
    On Mon, Jun 30, 2008 at 6:01 PM, Ben Schmidt ... Thank you Ben! The let &efm = substitute(&efm, ,%f:%l: (%c: ) ? zs ze%m, , , g ) works like a dream! I
    Message 1 of 9 , Jun 30, 2008
      On Mon, Jun 30, 2008 at 6:01 PM, Ben Schmidt
      <mail_ben_schmidt@...> wrote:
      >> Hi Ben,
      >> Here is my 'make' result file, it's so long, please be patient.
      > OK. Here's the line causing the problem:
      >> /bin/sh ../../libtool --tag=CC --mode=link gcc -g -O2 -Wall -g -O2 -
      >> o liblmtnone.la -rpath /usr/local/lmt/lib -version-info 1:0:0
      >> error.lo utils.lo environment.lo flock.lo ipc.lo signal.lo tellwait.lo
      >> pseudo_tty.lo ttymod.lo
      > And here's why:
      >> errorformat=...,%f:%l:%c:%m,%f:%l:%m,...
      > Errorformat is looking for (and finding!) something that looks like
      > filename:line-number:error-message
      > So it thinks everything up to the 1 in -version-info 1:0:0 is the file
      > name, the 0 in the middle is the line number, and the 0 and afterwards
      > is the error message.
      > I would suggest fixing it by requiring a space at the beginning of the
      > message. This should work for gcc/g++/etc. and most other tools. Putting
      > this line in your .vimrc should do it:
      > let &efm = substitute(&efm,',%f:%l:\(%c:\)\?\zs\ze%m,',' ','g')
      > This 'edits' the existing 'efm' option, adding the required spaces,
      > rather than setting an entirely new one.
      > If this fix also stops it recognising errors you want it to find, we
      > will have to think of something else, but I think it's likely to work.
      >> I don't understand what you said about ':compiler', but I will try to
      >> learn.
      > Using :compiler is easy. You just do something like
      > :compiler gcc
      > and Vim automatically sets the errorformat option correctly. It has to
      > know about the compiler, of course, and the files that describe all the
      > compilers it knows about are in $VIMRUNTIME/compiler (usually something
      > like /usr/local/share/vim/vim71/compiler). They are also documented at
      > :help :compiler.
      >> On the other hand, the 'errorformat' string to me is very hard
      >> to understand.
      > Yes. It's horrible, isn't it? It takes me quite a bit of effort to
      > decipher it, too, so I avoid it as much as I can!
      > Ben.

      Thank you Ben! The "let &efm =
      substitute(&efm,',%f:%l:\(%c:\)\?\zs\ze%m,',' ','g')" works like a
      dream! I think I will spend some time to study the syntax involved.
      And, I hope I can reach back to when I get other troubles. Thank you
      very much!

      You received this message from the "vim_use" maillist.
      For more information, visit http://www.vim.org/maillist.php
    Your message has been successfully submitted and would be delivered to recipients shortly.