Re: code_check stalled?

2010-01-11 Fir de Conversatie Birgi Tamersoy
Hello George, Yeap, unfortunately there haven't been any updates in the last year. I was extremely busy with the school, and could not find a long enough break to get back to the project. However, this is the second ``heads-up'' I got in the last four weeks or so (first coming from Martin Kopta

Re: Google summer of code

2009-02-06 Fir de Conversatie Birgi Tamersoy
Hello Bram and all, I was one of the previous students. This summer I was planning to finish what I had started (the code checking extension, since I am a graduate student, working on it during the semesters is extremely hard). I am totally flexible about how to do this: 1. I can re-apply as a

Re: Build failure for vim_extended with Vim 7.2.065

2008-12-08 Fir de Conversatie Birgi Tamersoy
, or there is another common way of doing it. I will fix it accordingly. Regards, On Mon, Dec 08, 2008 at 08:37:11AM +0100, Markus Heidelberg wrote: Birgi Tamersoy, 08.12.2008: Hello Markus, On Mon, Dec 08, 2008 at 01:10:20AM +0100, Markus Heidelberg wrote: Richard Hartmann

Re: Build failure for vim_extended with Vim 7.2.065

2008-12-08 Fir de Conversatie Birgi Tamersoy
Hello Markus, On Tue, Dec 09, 2008 at 03:38:30AM +0100, Markus Heidelberg wrote: Currently the code_check.txt help file also has the *intro* and *progress* keywords which overwrite the default goals to intro.txt and the progress filetype. Could this be adjusted? Yes, I can adjust that. I

Re: Build failure for vim_extended with Vim 7.2.065

2008-12-07 Fir de Conversatie Birgi Tamersoy
a message to Birgi Tamersoy. I'm not sure he reads this list. -- There are 10 kinds of people: Those who understand binary and those who don't. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org

Re: Build failure for vim_extended with Vim 7.2.065

2008-12-07 Fir de Conversatie Birgi Tamersoy
Hello Markus, On Mon, Dec 08, 2008 at 01:10:20AM +0100, Markus Heidelberg wrote: Richard Hartmann, 07.12.2008: Hi all, building vim_extended with the code checker patch fails: % git checkout -b local/code_checking origin/vim % git merge origin/code_checking % ./configure

Re: Highlight a particular line

2008-09-18 Fir de Conversatie Birgi Tamersoy
:21PM +0200, Bram Moolenaar wrote: Hongmin wrote: Hi everyone, I want to implement something like Flymake in Emacs. So I want to highlight the lines that has syntax errors. Can anyone provide any guidance on how to do that given the line number? Thanks! Birgi Tamersoy has been

Re: Highlight a particular line

2008-09-18 Fir de Conversatie Birgi Tamersoy
Hey Hongmin, On Thu, Sep 18, 2008 at 09:17:32PM -0400, Hongmin Fan wrote: Hi Birgi, I tried out your code, it works pretty well. Although what I thought of was something like an external plugin, working at the source code level definitely gives most flexibility. We thought if we

On-the-fly syntax checker version 0.1 :)

2008-08-18 Fir de Conversatie Birgi Tamersoy
|progress| + +== +1. What is CodeCheck *intro* + +*** CodeCheck is sponsored by Google under Google Summer of Code program, +mentored by Bram Moolenaar and implemented by Birgi Tamersoy. *** + +CodeCheck is an on-the-fly

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

2008-04-21 Fir de Conversatie Birgi Tamersoy
On Apr 21, 10:09 pm, Lin [EMAIL PROTECTED] wrote: Congradulations, Birgi! Thank you very much Lin :), I am very happy to be involved. Don't know whether you have looked into anything about Eclipse, but I referred to their documentation and learned a lot there. They also talked about how

Re: GSOC: that compiler/yacc book I mentioned...

2008-04-14 Fir de Conversatie Birgi Tamersoy
Thanks a lot, it seems to be a valuable resource. Regards, Birgi --~--~-~--~~~---~--~~ You received this message from the vim_dev maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---

Re: GSOC: On-the-fly Code Checking for Vim - Challenges

2008-04-13 Fir de Conversatie Birgi Tamersoy
Hey everybody, I'm not really because I program mainly in C++, and my experience demonstrates that after the first error it is not uncommon to have the compiler completely lost. Thus I know this will be a very complex task, and I'm not sure it can be done. After your posts I made a small