Plugins you should put in your vimrc • Hacker News Board

Re: Plugins you should put in your vimrc

#31

Post by derwiki » Mon, Sep 03, 2012, 3:11 PM UTC

Hates_ wrote: post #4

I've moved to ctrlp over Command-T as it's pure Vimscript. Feels even faster than Command-T to me: https://github.com/kien/ctrlp.vim

How many files is the project you try it on? CommandT is faster for me, but only noticeably on large projects.

Re: Plugins you should put in your vimrc

#32

Post by matthiasv » Mon, Sep 03, 2012, 3:12 PM UTC

qznc wrote: post #5

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

It also renders Buffer Explorer obsolete, if used with buffer search mode.

Re: Plugins you should put in your vimrc

#33

Post by petepete » Mon, Sep 03, 2012, 3:14 PM UTC

I 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

Re: Plugins you should put in your vimrc

#34

Post by georgebashi » Mon, Sep 03, 2012, 3:16 PM UTC

dqminh wrote: post #17

qznc wrote: post #5

I 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'] It lets CtrlP use git to list files, which is much faster for large project

I've tweaked mine to this, which includes untracked files, but honours your gitignores:

  let g:ctrlp_user_command = ['.git/', 'cd %s && git ls-files --exclude-standard -co']

It was annoying me that I couldn't open files I'd just created with CtrlP, as they wern't yet tracked.

Re: Plugins you should put in your vimrc

#35

Post by matthiasv » Mon, Sep 03, 2012, 3:17 PM UTC

intractable wrote: post #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/ultis…

Actually, where's the love for neocomplcache? [1]

neocomplcache is actively maintained and well documented, not to mention supporting many more features, such as file path completion, register completion, omni completion and Vim completion.

[1] https://github.com/Shougo/neocomplcache

Re: Plugins you should put in your vimrc

#36

Post by d0m » Mon, Sep 03, 2012, 3:20 PM UTC

I clicked the article thinking "Please, don't say Surround, Cmd-T, snipmate or Buffer Explorer".. These are amongst the most popular plugins for Vim and every week there are blogs saying exactly the same thing.

Note: I have nothing against this blog in particular.. but please, upvoters, try to upvote new stuff.

Re: Plugins you should put in your vimrc

#37

Post by matthiasv » Mon, Sep 03, 2012, 3:21 PM UTC

petepete wrote: post #33

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

Re: Plugins you should put in your vimrc

#38

Post by aravenel » Mon, Sep 03, 2012, 3:21 PM UTC

qznc wrote: post #5

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

Agreed. I used to use Command T religiously, but I move machines frequently due to the nature of my work and was spending more time trying to get it and its dependencies working on the variety of machines that I use than I was actually, you know, coding.

Granted, Ctrl-P is much slower than Command-T. Won't deny it. But carefully excluding all .git, virtualenv (for python) and similar folders in my .vimrc, along with making sure I cd into a directory a little closer to my code makes it almost as quick for me. And it just works, which is invaluable in my book.

Re: Plugins you should put in your vimrc

#39

Post by gaving » Mon, Sep 03, 2012, 3:31 PM UTC

intractable wrote: post #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/ultis…

+1 for ultisnips, definitely the superior option when it comes to templating.

Re: Plugins you should put in your vimrc

#40

Post by intractable » Mon, Sep 03, 2012, 3:31 PM UTC

d0m wrote: post #36

I clicked the article thinking "Please, don't say Surround, Cmd-T, snipmate or Buffer Explorer".. These are amongst the most popular plugins for Vim and every week there are blogs saying exactly the same thing. Note: I have nothing against this blog in particular.. but please, upvoters, try to upvote new stuff.

I agree.

But, I must say: no matter how repetitive these articles, I pick up something new in the HN comments every single time.