This is perfect since I'm just starting with vim.
Plugins you should put in your vimrc
41–50 of 99 posts
Re: Plugins you should put in your vimrc
#42Earlier quoted context omitted.
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.
I had to weed out all the crap that I had accumulated in ~/.vim/ over the years :)
Re: Plugins you should put in your vimrc
#43Earlier quoted context omitted.
As I posted above, there's Vundle: https://github.com/gmarik/vundle You just copy your .vimrc over and Vundle installs everything.
Vundle seems like it only takes care of the plugins. I'm looking for a vim install system, like Python's setup.py.
The rage these days seems to be to keep your own dotfiles repo, complete with some kind of install mechanism.
My own is here [1] but it covers my whole homedir, not just VIM. I use Rake tasks (originally inspired by @holman, I believe) for install / update / clean.
There is a bootstrapping problem when using Vundle with many plugins [2]. The only way to have your Vundles install cleanly the first time is to split up .vimrc into two separate files, which is what I have done.
[1] https://github.com/anthonywilson/dotfiles
[2] http://www.gmarik.info/blog/2011/05/17/chicken-or-egg-dilemm...
Re: Plugins you should put in your vimrc
#44I prefer CtrlP to CommandT, since it does not requires external programs. https://github.com/kien/ctrlp.vim
As others have said CtrlP is slower; but not having the Ruby dependency makes it _far_ less of a headache to install on Windows, should you ever find yourself on such a machine.
Re: Plugins you should put in your vimrc
#45Every time an article like this comes up, snipMate seems to be mentioned. This particular author even pointed to the old repository which appears unmaintained and has not had a check-in for two years. Where's the love for UltiSnips? [1] UltiSnips is actively maintained and well documented, not to mention supporting many more features, such as Python interpolation. More info at [2]. [1] https://github.com/SirVer/ultis…
+1 for ultisnips, definitely the superior option when it comes to templating.
Can you elaborate?
Re: Plugins you should put in your vimrc
#46installing snipmate through pathogen is still a dark art
Re: Plugins you should put in your vimrc
#47This is perfect since I'm just starting with vim.
In my experience, it's better to spend a long time playing with Vim, and then look at plugins. There's a lot that Vim does out of the box without any additional tools, and spending time learning to use (some) of it without trying to make it more like another editor is the only way you're going to get better at it. Learn about buffers and how to manage them before using BufExplorer. Learn the (many) movement keys, and insertion, append, replace, substitue, change, options before you use Surround.
It may sound odd, but learn to use the tool by itself before you try and plugin anything else, otherwise you'll just get lost.
Re: Plugins you should put in your vimrc
#48I already happen to have these in my setup; if you're a git user I highly recommend fugitive.vim too. https://github.com/tpope/vim-fugitive
I tried to incorporate it in my workflow several times, but usually I end up ing the Vim process and commit, branch etc. via the command line. I understand that Fugitive _might_ help resolving merge conflicts, but this is really just a small percentage of my daily Git workflow. Maybe, there is some deeper sense in it that I haven't grasped yet?
try this:
:Gdiff
Re: Plugins you should put in your vimrc
#49Earlier quoted context omitted.
Vundle's better.
Not sure why you've been downvoted. I agree with your vundle suggestion. I migrated from pathogen to vundle and would recommend that people using the former check out vundle again. Even if it's from the 'wrong author' (aka not from tpope).
> Not sure why you've been downvoted.
Just stating "X is better" without giving any reason is not particularly helpful.
Re: Plugins you should put in your vimrc
#50Every time an article like this comes up, snipMate seems to be mentioned. This particular author even pointed to the old repository which appears unmaintained and has not had a check-in for two years. Where's the love for UltiSnips? [1] UltiSnips is actively maintained and well documented, not to mention supporting many more features, such as Python interpolation. More info at [2]. [1] https://github.com/SirVer/ultis…
+1 for ultisnips, definitely the superior option when it comes to templating.
I just installed it. It's pretty good. The docs aren't great though. I hate sitting through screencasts.