Live data from Hacker News

Plugins you should put in your vimrc

vimninjas.com

21–30 of 99 posts

Re: Plugins you should put in your vimrc

#21
post #9

Thank 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.

Vundle seems like it only takes care of the plugins. I'm looking for a vim install system, like Python's setup.py.

Re: Plugins you should put in your vimrc

#22
post #10

Earlier quoted context omitted.

pathogen

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).

Re: Plugins you should put in your vimrc

#23

Earlier 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).

The only difference I'm aware of (I haven't looked into it much) is that Vundle downloads plugins too, rather than just install them, but it's a pretty big difference when you're looking for a plugin manager.

Re: Plugins you should put in your vimrc

#26
post #21

Earlier 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.

Can you elaborate on your requirements/wishes here?

For me my vim environment consists of my vimrc plus plugins. Granted, I pick plugins based on the "doesn't need extra steps to work" requirement.

vundle therefor restores my setup completely from a (potentially restored or managed in a git repository) vimrc file. What's missing for you?

Re: Plugins you should put in your vimrc

#27
post #20
post #5

I 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.

Are they already open / matched by wildignore?

Re: Plugins you should put in your vimrc

#28
post #5

I prefer CtrlP to CommandT, since it does not requires external programs. https://github.com/kien/ctrlp.vim

For the repo I work in, CtrlP takes about 3 seconds to load for the first time; CommandT is instant. CtrlP is nice for smaller projects, though.

Re: Plugins you should put in your vimrc

#30
Every 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/ultisnips

[2] http://fueledbylemons.com/blog/2011/07/27/why-ultisnips/

Post reply on HN