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

51–60 of 99 posts

Re: Plugins you should put in your vimrc

#51

Post by mjhoy »

matthiasv wrote: post #37
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?

That's what I do, too. I keep it around for :Gblame.

Re: Plugins you should put in your vimrc

#53

Post by wahnfrieden »

StavrosK wrote: post #23
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).

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.

It's huge because it lets me manage my plugins in source control much more easily than juggling submodules in git or whatnot. Instead I just have my plugins as lines in my vimrc.

Re: Plugins you should put in your vimrc

#55

Post by wahnfrieden »

gnosis wrote: post #7

My favorites: * pathogen [1] * PreciseJump [2] * MRU [3] * scratch [4] * xptemplate [5] * renumber [6] [1] - http://www.vim.org/scripts/script.php?script_id=2332 [2] - http://www.vim.org/scripts/script.php?script_id=3437 [3] - http://www.vim.org/scripts/script.php?script_id=521 [4] - http://www.vim.org/script.php?script_id=389 [5] - http://www.vim.org/scripts/script.php?script_id=2611 [6] - http://www.vim.org/scripts…

Use vundle instead of pathogen - it installs the plugins for you, so managing them in source control is much easier. Lines in a vimrc are much less of a headache than git submodules etc.

Re: Plugins you should put in your vimrc

#56

Post by begriffs »

I recently "declared vim bankruptcy" and rebuilt my vimrc from scratch. I want a full-featured vim, but I want to keep it responsive.

There are many fancy presets out there https://github.com/skwp/dotfiles https://github.com/carlhuda/janus https://github.com/spf13/spf13-vim https://github.com/vgod/vimrc but they freak me out. They turn vim into a singing, dancing, syntax/spell checking, indexing, buffer Whack-a-mole. My philosophy is that vim shouldn't do anything behind your back, but it should do great things if you ask.

  * Jumping to definitions
  * Finding all uses of a symbol in a repo
  * Running things
    + A test
    + Code in a repl
  * Git blame, diff
  * Summarizing methods in open file
  * Navigating my (rails) app
When putting this together, I found Vundle to be the easiest package manager. Just specify any desired vim plugin github repos in your vimrc and let the :BundleInstall, :BundleClean etc commands do the rest.

I used the standard plugins for most of the stated objectives, but there are places where I found some tricks. The coolest trick is running external programs without locking vim. You can send commands and selections to a tmux terminal using Vimux: https://github.com/benmills/vimux After wrangling with running vim under tmux, I discovered that the vimux plugin works in MacVim too when tmux is running alongside.

The thing I run most often is tests. In Rubyland people advise using Guard, which runs tests automatically when test files change. However this goes against my "don't do things behind my back" philosophy. Vim-turbux is more my taste. It extends vimux to run cucumber and rspec tests with the press of a key: https://github.com/jgdavey/vim-turbux

The next area where most megadotfile presets are lacking is finding the uses of code. Finding code definition is pretty well handled by exuberant-ctags and vim-rails, but finding code uses is trickier. The cscope utility does this, but its language support is limited from what I could tell. Another contender is GNU global. Its setup is...interesting: http://simple-and-basic.com/2008/10/using-rtags-ang-gtags-fo... I couldn't get it working and the GTAGS files it generates cluttered my repos. I cheated and just mapped a key to do :Ggrep (git-fugitive) on the current word. While cscope or global would give the finest results, a massive grep comes close. Let me know, anyone, if you've gotten the tagging systems working better.

My work in progress is here: https://github.com/begriffs/dotfiles I'd appreciate any criticism; I have lots to learn.

Re: Plugins you should put in your vimrc

#58

Post by darklajid »

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.

Agreed, but he replied to a single word comment (=> worse)

Re: Plugins you should put in your vimrc

#59

Post by rbonvall »

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…

While the original author has abandoned snipmate, there is a fork that is actively maintained: https://github.com/garbas/vim-snipmate

I've been a happy user of snipmate, but I'll give ultisnips a try. Thanks for the tip!

Re: Plugins you should put in your vimrc

#60

Post by latortuga »

qznc wrote: post #5

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

A bunch of people have posted about Ctrl-P being slow but I've never had that problem. Here's my user_command:

    let g:ctrlp_user_command = "find %s -type f | egrep -v '/\.(git|hg|svn)|solr|tmp/' | egrep -v '\.(png|exe|jpg|gif|jar|class|swp|swo|log|gitkep|keepme|so|o)$'"
While the CtrlP window is open, hitting F5 will refresh the list of files and it's really fast. I'm on an SSD but it's still basically instant on every project I code in. I think it must have a slow default which gives people the impression that it's slow. After using both FuzzyFinder and Cmd-T for a long time, CtrlP has been easily the best of the bunch.
Post reply on HN