Two New Vim Plugins | Hacker News Reader

Two New Vim Plugins

ithaca.arpinum.org

33 pointstelemachos15 comments

Another alternative to Pathogen is Vundle (https://github.com/gmarik/vundle). I've been using this one for a while and really enjoy it.

ha, you beat me at it. I typed the post and got back to Campfire alerts at work and found yours :)

thing I love about Vundle is that it makes it really really simple to maintain your vim stuff. Your whole vim setup is down to just your .vimrc

My initial feeling is that I prefer modular to bundled in this case. That is, I use shell scripts or small programs to mass-install or mass-update bundles, and I'm not sure I want all that information in my .vimrc. That said, I can definitely see why some people might love it, and Vundle itself looks interesting. I'll definitely take a look.

@SingAlong (I can't reply to your reply, so I'm replying here.)

> Vundle does exactly that - makes installs and updates easier.

I know. But that's what I meant by "I prefer modular to bundled in this case": I don't want all of that in one place (my .vimrc). I'm not saying Vundle is bad or that this is a wrongheaded way to do things. It just don't fit my preferences.

Vundle does exactly that - makes installs and updates easier.

So you add: Bundle "rails.vim"

to your .vimrc and then in vim you do :BundleInstall! and it updates all the bundles. The "!" suffix also updates plugins already installed. Also makes it easier to specify github sources. Instead of just rails.vim, you specify "tpope/rails.vim" and it'll get the repo from tpope's github repository.

Might be offtopic, but out of curiosity could you share your vimrc? I've only been using vim for about a year now and I have a pathetic vimrc here https://github.com/HashNuke/dot-files/blob/master/.vimrc

EDIT: (coz i can't reply to comments)

@johncoltrane I thought the statusline was the same as modline. When I created that file, I took someone else's vimrc and added stuff until there was no trace of borrowing (except the one you caught).

@telemachos thanks for sharing

Wondering why I'm not able to post replies to comments. @telemachos too said the same a whiie back.

I'm not sure if you're asking me or Legion, but I'm happy to share mine: https://github.com/telemachus/dotfiles/blob/master/vim/vimrc.

Looking at it now, I can already see a handful of places I want to update it. Dotfiles are non-stop yak shaving.

1 year old Vim user here, too.

If you don't mind my curiosity, at line 167/8, you have

    " make filename and status always visible
    set modeline

but that's unrelated to the statusline, modelines are special comments containing file-specific settings you put at the top of a file. This line just activates support for the feature.

i don't think there is such a thing as a pathetic .vimrc. Some people have 2 000 lines of custom mappings in their .vimrc, others have 10 lines. That's Vim.

> Wondering why I'm not able to post replies to comments.

I think this was a switch designed to stop flame-wars or overly nested discussions. (I remember I used to be able to comment on comments.)

Still, it makes it very hard to have conversations.

Figured out how to comment. Just visit a comment's page drectly and you'll find a reply box there. So I had to use that "link" link in your comment and then use the box on that page.

There's actually code that throttles the level of nesting comments to prevent a IRC like flamewar or even just vacuous comments that have not been well thought out; the deeper the nesting, the longer you have to wait until you are allowed to comment on that post.

Edit: your way works too if you want to short circuit that delay.

I don't like having my Vundle stuff cluttering up my .vimrc either.

Which is why I have all of that extracted to a separate file, which .vimrc sources.

I do this for a lot of things, allowing .vimrc to be purely about vim settings (and then some source commands at the end to pull in the external files).

Vundle is trying to emulate Bundler, so it seemed only fitting that I move everything into a Gemfile-like bundle definition file: https://github.com/LegionSB/dotfiles/blob/master/vim/configs...

Agreed. Vundle is amazing. I'm using it my vimrc (https://github.com/mutewinter/dot_vim/blob/master/vimrc#L18).

I've been trying to replicate the filetype specific bundles using pathogen's disabled bundle feature, so unbundle is a nice discovery. To allow for more flexibility such as enabling a bundle for more than one filetype but not all (e.g. just jvm languages), there can be a separate directory that contains all bundles, and these can be symlinked from ftbundle and bundle. This also allows disabling bundles that you're still testing.

There's an awesome ruby gem called vimpack (http://github.com/bramswenson/vimpack) that makes it easy to install any VimL plugins from github directly, a la `vimpack install git@github.com:user/neat_vim_plugin.git` It uses pathogen on the backside to load the plugins. It also provides easily cloning your repo for use elsewhere. It's how I manage my vim configuration amongs multiple different computers / other developers can use my repo as a starting point. I <3.

So, Unbundle sounds like Vim's ftplugins. Are there global plugins out there that work for a single filetype and interfere with other filetypes?

Reply on news.ycombinator.com