Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Plugins you should put in your vimrc

vimninjas.com

Post reply on HN
Print view View original

71–80 of 99 posts

Re: Plugins you should put in your vimrc

#71

Post by naglfar »

thurn wrote: post #54

Emacs versions to check out: Surround: wrap-region ( https://github.com/rejeep/wrap-region ) Command-T: ido-mode with ido-find-file snipMate: YASnippet Syntastic: flymake Buffer Explorer: ibuffer

I actually tried really hard to get ido-mode to recursively search files under the current directory, but I was never successful.

Is there some really easy modification I have overlooked? Because that is one of the major advantages CtrlP or Command-T have - and trying to use https://github.com/emacs-helm/helm with https://github.com/bbatsov/projectile turned out to be by far too slow.

Re: Plugins you should put in your vimrc

#72

Post by tomku »

mun2mun wrote: post #69
ConstantineXVI wrote: post #44

Earlier quoted context omitted.

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.

Installing command-t is fairly easy on windows. Just compile as instructed with latest ruby 1.9 + devkit and replace gvim.exe with the one specified in this page https://wincent.com/comments/6544 .

That's a perfect example of something that is both easy AND a headache. It's not certainly difficult to do, but I don't want to be replacing my gvim executable with one provided by an anonymous forum user just to make one script work. Ignoring the potential security issue, what happens when I want to upgrade vim, or run another script that's similarly "easy" to install on Windows?

I can't speak for other vim users, but I haven't had a lot of luck with distro versions of vim and Ruby/Python extension scripts on Linux either. After fighting with it for a while, I ended up just declaring my .vimrc to be a VimScript-only zone. It sucks losing Gundo and Command-T and a couple other great plugins, but it's done wonders for my sanity, and everything works well on Windows as a bonus.

Re: Plugins you should put in your vimrc

#73

Post by ConstantineXVI »

mun2mun wrote: post #69
ConstantineXVI wrote: post #44

Earlier quoted context omitted.

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.

Installing command-t is fairly easy on windows. Just compile as instructed with latest ruby 1.9 + devkit and replace gvim.exe with the one specified in this page https://wincent.com/comments/6544 .

Not quite as easy as installing vanilla vim and dropping my ~/.vim (IIRC it's ~\_vim on windows) in place without touching anything.

Re: Plugins you should put in your vimrc

#74

Post by mun2mun »

tomku wrote: post #72
mun2mun wrote: post #69

Earlier quoted context omitted.

Installing command-t is fairly easy on windows. Just compile as instructed with latest ruby 1.9 + devkit and replace gvim.exe with the one specified in this page https://wincent.com/comments/6544 .

That's a perfect example of something that is both easy AND a headache. It's not certainly difficult to do, but I don't want to be replacing my gvim executable with one provided by an anonymous forum user just to make one script work. Ignoring the potential security issue, what happens when I want to upgrade vim, or run another script that's similarly "easy" to install on Windows? I can't speak for other vim users, b…

Well the forum is not actually an anonymous forum, the site owner is creator of command-t plugin. When I encountered crash after installing command-t after upgrading to 7.3 almost 1.5 years ago the first google search led me to that page (now first result is this page http://chrislaco.com/blog/gettimg-command-t-working-on-windo..., even better with instruction).

I also had no problem installing it in Ubuntu/Mint. Just removed vanilla vim and installed vim-gtk and then compiled command-t.

Command-t is actually my only non-vimscript plugin in my plugin list, and it is rightfully so :). I tried to cope with CtrlP, but it feels too slow for me for large collection of files. Also its fuzzy matching is not on par with command-t. I have actually no problem to take this little hassle to install command-t for performance consideration :).

Re: Plugins you should put in your vimrc

#75

Post by lengarvey »

davidarkemp2 wrote: post #47
karmicthreat wrote: post #41

This 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…

I'd say that it's better to start off with installing vundle (https://github.com/gmarik/vundle/) and then whenever you feel like you're having problems doing something like file/buffer navigation, auto-completion or making vim pretty then go out looking specifically for something you like and vunlde will make it really easy to install just by pointing at the github.

Whatever you do, don't install syntastic unless you want your vim to run awfully slow.

Re: Plugins you should put in your vimrc

#76

Post by icambron »

davidarkemp2 wrote: post #47
karmicthreat wrote: post #41

This 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…

I disagree. As someone who started using Vim recently, the issue wasn't learning modes/key sequences as it was just reaching feature parity with my previous editor (note that doesn't mean "acts like my previous editor", just "is at least as capable as my previous editor"). If I can't open files really quickly, I feel lost and upset, so I took care of that very early in the learning process by setting up CtrlP. Same with some other plugins.

More generally, to me, the features that happen ship with Vim aren't special. I want the best editor for me, which might require features the builders of Vim didn't want to include. Vanilla is just another flavor.

Re: Plugins you should put in your vimrc

#77

Post by tomjakubowski »

johnkchow wrote: post #57

One of my favorite plugins that hasn't been mentioned so far is vim-powerline https://github.com/Lokaltog/vim-powerline . It makes Vim have a really polished look to it, and more important: tells you which Git branch you're currently in.

For me, vim-powerline gives a much stronger visual indicator of the current mode. Changing the color of the whole statusline really stands out.

Re: Plugins you should put in your vimrc

#78

Post by jlgreco »

StavrosK wrote: post #11
rane wrote: post #10

Earlier quoted context omitted.

pathogen

Vundle's better.

Does Vundle allow you to just unzip plugins that aren't hosted anywhere into their own subdirectory somewhere inside your ~/.vim/ like Pathogen does?

This isn't clear from it's webpage.

Re: Plugins you should put in your vimrc

#79

Post by goatslacker »

tux1968 wrote: post #8

Have to agree with the author about his picks. Excluding a couple programming-language specific plugins the only other ones that i'd include on a longer list would be: EasyGrep - A nice quick way to search for arbitrary text when ctags/cscope doesn't have the answer. https://github.com/vim-scripts/EasyGrep QuickFixSigns - Show marks associated with each line in a buffer. Also shows lines that have been changed from w…

Definitely give supertab a shot. It's recently become one of my favourite plugins and now I'm tabbing religiously

Re: Plugins you should put in your vimrc

#80

Post by slurgfest »

ch0wn wrote: post #49
darklajid wrote: post #22

Earlier quoted context omitted.

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.

pathogen requires you to roll your own submodule thingy. This is certainly feasible if you know git well, but vundle is still easier
Post reply on HN