Excerpts from Martin Kopta's message of Tue Nov 03 00:32:50 +0100 2009:
> 
> Hi, I wrote a blogpost about Codecheck (on-the-fly code checking):
> 
> http://dum8d0g.blogspot.com/2009/11/on-fly-code-checking-in-vim.html

I tried adding a comment but I could'nt login.

> Codecheck is nice idea and it is well done
I tried it some month ago. There are some screen update issues as well.
So you don't get immediate feedback in all cases.  Example C / C++. I
remember that if you run the bg compilation on a .c included header
files are ignored. Thus if you have an error in the header file
no red lines will appear.
The truth is that you can just use CDT and you get some more features
such details about macro expansion and nice browsing features.
Syntax checking is done in a cached incremental way so it's much faster.
You get decent completion for free. It may or may not work for your project. I
recommend you trying both and use the tool which fits your task you have
to solve.  I'd like to see some more development on these issues. But I
also see that this means a lot of work. I tried making vim more thread
safe following similar ideas. I gave up after three days because
there are many different back ends to test and getting to know all the
corners of the vim C code takes a lot of time I don't have.

But I have implemented yet another solution to this:
You can start a background process (either using python or sh&) and call
back into vim utilizing the client server. So you don't have to do any
patching. When the thread calls back into vim you can load the error
list into quickfix. You can start the process automatically using buf
write autocommands. This works pretty well in practise.

Yet another attempt is eclim which could solve this task.

Maybe its worth adding a link to your explanation of the experimental
feature on http://vim.wikia.com/wiki ?

Marc Weber

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to