[email protected] wrote:
> A plugin to create and manage my projects as an IDE (Visual Studio).
Hi. First of all, vim is NOT an IDE, it's a text editor.
An IDE compiles many programs into a big one whereas vim is just a
(powerfull) text editor with many features.
For example, to see all your dirtree, :Sex or :Vex

> A plugin to use GDB and also to put Breakpoints from the lines of sources 
> codes in gVim.
Keep in mind that vim has built-in functionnalities, you do not need a
plugin for everything !
I once known a way to set breakpoints from within vim. Anyway, in the
same spirit, check :help quickfix. It gives you the errors issued from
compilation and lets you navigate the lines that caused the errors.

> A plugin for the completion of sources codes, for example for functions and 
> vars from libc, for functions and vars from extern lib and from my own 
> sources files.
:help ins-completion    | all built-in completion (really powerfull)
:help ctags             | generate tags file with ctags -R
                        | then, :set tags=/path/to/you/tags
:set omnifunc=syntaxcomplete#Complete
<Ctrl-X><Ctrl-O>        | will complete with tag file and syntax
                        | specific stuffs.
<Ctrl-X><Ctrl_I>        | will complete with included files (stdio.h,..)

> A plugin to build/compile a project.
That's what Makefiles are made for :)
:make to invoke makefile from within vim (note that 'make' can be tweak
to launch something else than 'make', like gcc, javac, perl, etc...


Obviously, those "built-in" function are well integrated into big
plugin to make them *prettier* and *easier to use*:
    - project.vim
    - NERDTree.vim
    - BreakPts.vim
    - SuperTab.vim
    - SnipMate.vim
    - ...

There are tons of plugins that do tons of things... BUT I suggest that
you first learn VIM, the editor, the powerfull editor.
Every thing done with a plugin can be done without it, with more or less
pain... But if you find that a task you do frenquently is painfull, you
might tough of creating a function or using a plugin.

Please, try to do stuffs before relying on plugins. Your vim experience
will be better :)

> Thank you very much.
You're welcome ;)

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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to