The drop-down list is a good one. I was thinking about putting the
error/warning messages at the info line (the place where VIM usually gives
error messages, and file information; I don't know what it is called). Both
are viable. What do you think? I am worrying about like very long messages,
and the conflict with other features, or confusing user by overloading the
same area for too many uses.

Yeah, I can work on the 'errorformat'. If we just re-use 'errorformat', here
is an assumption that the on-the-fly syntax checker uses the same error
format as 'makeprg'. Probably we should have a variable 'cc_errorformat',
which is similar to 'errorformat', but dedicated to CodeCheck.

I'm reading the code, it's a little bit tough because of my unfarmilarity of
VIM source code itself. Hopefully it will turn better.

Hongmin

On Thu, Sep 18, 2008 at 11:57 PM, Birgi Tamersoy <[EMAIL PROTECTED]>wrote:

>
> 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 implement it this way, we can extend it more easily.
> Also, since now it directly uses a compiler in the background, it
> catches all the compile-time errors.
>
> > I think it would be great if it prints
> > out the compiler's error/warning message when the cursor is located on a
> > syntax-incorrect line.
>
> I totally agree with you. I think this actually is a ``must-to-have''
> feature. A drop-down list of errors on that line definitely increases
> the usability. Are you familiar with the ``keyword completion''? If so,
> what I mean is a similar drop-down list. What do you think?
>
> > I would like to help out to support more languages,
> > maybe take advantage of the 'errorformat' string...
>
> It will be great if you can add such a functionality using the
> ``errorformat'' string. After that, in order to support a new
> language/compiler(interpreter), we would only need to define the
> ``errorformat'' of the new compiler(interpreter).
>
> At the moment I am working on the Windows support. I have 0 experience
> on cross-platform development, so it takes some time to figure out how
> things are working. Since, Windows support does not have serious effects
> on the existing code, you can freely work on language support.
>
> > Best,
> > Hongmin
>
> Please let me know if you need some help with the existing code.
>
> Best regards,
> --
> Birgi
>
> >
>

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

Raspunde prin e-mail lui