> Allright, I see the point.
> I will look into VAM, and go on looking for individual plugins, if I
> think I need one.
> I have one question left.
>
> \quote: "we have rudimentary support for most
> programming languages bundled with vim."
>
> How can I learn more about that? I cannot find anything about that
> with google.
> It would really help me if I knew how to compile or debug source-code,
> from within vim.
>
> Greetz,
>
> Chiel
>
> --
> You received this message from the "vim_dev" 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
>


Yeah. Rudimentary was meant as "syntax highlighting mostly".

As far as debugging goes: you have plugins that handle gdb
integration, and the :make command can invoke the appropriate make
tool if you set it. Eclim provides Java debugging (I think).

Honestly, I'm not the right sort of person to ask about debuggers -
I've always thought debugging was a place for the debugger and not an
editor. (I also favor printf debugging, but that's just me).

Compiling is also a job for the shell and make tools and not for the
editor. If you want your build configured correctly, no editor is
going to be sufficient for that (I am *not* talking about IDE's here,
which vim *isn't* (although it does a pretty good job). Even visual
studio doesn't do much good in that regard - I'm usually stuck with
cmake even on windows, because I hate the idiotic compiler flag GUI
that visual studio provides. Again, that's just me.


Summary:
So, as far as compiling goes then, you're stuck with whatever you
program into your vim :make hook (meaning, find your compiler plugin).

There are plugins to support debuggers. I can't attest to their quality.

There are plugins that highlight errors in source code (compiler
plugins and clang_complete).

As to how you can learn more about language support within vim... see
the vim wiki link in my previous email. Search for the target
language, it might have some pointers.

:he target-language could help too  (as in :he haskell)

regards,

G

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

Raspunde prin e-mail lui