VimClojure – Easy
October 12th, 2011
Update 1/2013: The future of Clojuring with Vim is tpope’s foreplay.vim. You can find a tutorial here.
I promise this is the last VimClojure post for a while.
I get the feeling that my post describing my VimClojure setup is a little too involved, especially for someone that just wants something working quickly. Also, from what I’ve seen on #clojure, there’s some frustration out there. With that in mind, I put together a minimal example configuration with instructions.
So, without further ado, vimclojure-easy.
Feedback welcome.
I fumbled with your “high octane” VimClojure setup a couple of times, including just the other day. I’ve looked at your VC-easy before, but I have a heavily tweaked .vimrc and a thoroughly infected pathogen installation (also tweaked), and I didn’t want to cast that aside.
Ultimately frustration drove me to it: I followed your procedure, backed up my existing config, blasted in your VC-easy, and dang! It worked right out of the box. Then I started chewing my nails about merging the two. I ran a couple of trees on each directory, and looked inside your .vimrc.
Wow! Merging was a snap!
It took me maybe 30 minutes … and that’s only because I was double- and triple-checking every move I made (mostly unnecessarily).
So now I have my beloved .vimrc, all my pathological plugins *and* your VimClojure config. Why, I even changed a couple of my plugins (from NERDtree to Command-T, e.g.), but I haven’t drunk the Vundle kool-aid yet.
I can’t believe no one has made any comment before now. You’ve provided a painless testbed, with a simple migration to “production” … and that, Sir, is a very valuable service indeed.
My deepest gratitude.
Tom.
@Tom Maynard
My pleasure :)
Thanks for the wonderful setup! I’m looking forward to seeing how clojure works inside of vim…