Any vim plugin post that doesn't contain Vundle is incomplete, in my opinion. How else are you going to manage all these plugins? https://github.com/gmarik/vundle
pathogen
Vundle's better.
Plugins you should put in your vimrc
11–20 of 99 posts
Re: Plugins you should put in your vimrc
#12Thank you for showing how to use the plugins, most of these articles don't. I looked at the rest of the site, bookmarked! Can I make an article suggestion though? I'm a new(ish) vim user that is always on different systems. I need a way to quickly install/remove my vim settings and plugins. A tutorial how to do this would be awesome. Take for granted vim and git are already installed, my ideal workflow would be somet…
Thoughtbot dotfiles (https://github.com/thoughtbot/dotfiles) works something like that. I've branched it for myself and extended it.
Re: Plugins you should put in your vimrc
#13Thank you for showing how to use the plugins, most of these articles don't. I looked at the rest of the site, bookmarked! Can I make an article suggestion though? I'm a new(ish) vim user that is always on different systems. I need a way to quickly install/remove my vim settings and plugins. A tutorial how to do this would be awesome. Take for granted vim and git are already installed, my ideal workflow would be somet…
As I posted above, there's Vundle:
https://github.com/gmarik/vundle
You just copy your .vimrc over and Vundle installs everything.
Re: Plugins you should put in your vimrc
#14Among the things I personally couldn't do without these days snipMate, which is mentioned in the article. Then there's clang_complete which made me very happy. Finally a compiler-based auto-completion for C in vim. Last but not least there's fugitive. That's really most of what I need since vim already provides a lot of useful features by itself.
Re: Plugins you should put in your vimrc
#15Re: Plugins you should put in your vimrc
#16I agree to these five, and add:
* matchit - extends % functionality to support HTML/XML tags and also functions, blocks, conditionals in many languages.
* Supertab - tab completion done right.
* Tagbar or Taglist - code tree browser.
Re: Plugins you should put in your vimrc
#17I prefer CtrlP to CommandT, since it does not requires external programs. https://github.com/kien/ctrlp.vim
i had trouble with CtrlP initialy because the initial load time is too slow. However, this config line fix it for me
let g:ctrlp_user_command = ['.git', 'cd %s && git ls-files']
Re: Plugins you should put in your vimrc
#18Any vim plugin post that doesn't contain Vundle is incomplete, in my opinion. How else are you going to manage all these plugins? https://github.com/gmarik/vundle
This, a hundred times over, after using vim for 4 years full time (e.g. pretty much 8 hours a day, and who knows how long before that intermittently) I finally took setup vundle, it was so worth all of the 600 or so seconds it took to get working.
Re: Plugins you should put in your vimrc
#19Any vim plugin post that doesn't contain Vundle is incomplete, in my opinion. How else are you going to manage all these plugins? https://github.com/gmarik/vundle
This, a hundred times over, after using vim for 4 years full time (e.g. pretty much 8 hours a day, and who knows how long before that intermittently) I finally took setup vundle, it was so worth all of the 600 or so seconds it took to get working.
Ten minutes is overstating it, even. I just downloaded the thing, pasted the other thing into my .vimrc, done.
Re: Plugins you should put in your vimrc
#20I prefer CtrlP to CommandT, since it does not requires external programs. https://github.com/kien/ctrlp.vim
I have strange issues with CtrlP, especially files not being found although they would be a clear match.