Because I’ll need to replicate this miracle at home later on my Windows machine, here’s the fresh slice of hell I endured to get Command-T running under Ruby 1.9.2, DevKit, GVim 7.3 on Windows 7. I’m assuming you already have some experience with GVim, vimrc, plugins and Ruby already.
Install Ruby 1.9.2
I’m assuming you have, but if you haven’t, install the latest Ruby for Windows:
My default install path was
Install the latest DevKit. The latest one, not the one listed on GitHub downloads.
I extracted DevKit into
cd C:\Ruby192\DevKit\ and ran the perscribed
ruby dk.rb init and
ruby dk.rb install
Install the latest GVim for Windows. I believe this moved from 1.9.1 to Ruby 1.9.2
Apparently, the latest GVim has some Ruby binding issues. See this thread for an updated binary from trunk.
Set Ruby Path
This may not be required, but I did it just for giggles. In your _vimrc add this:
let s:ruby_path = 'C:\Ruby192\bin'
Just to make sure you have a Gvim with a working ruby, issue this Gvim command:
: ruby 1
If you get an error, then lord knows. :-)
Download Command-T, Compile and Install
Get the latest Command-T source from GitHub:
git clone https://github.com/wincent/Command-T.git yourvimfiles\plugins\commandt
In gemeral, I had 2 problems. First, the rake file seems broken on windows as it uses &&. Second, while my usually command prompt did gem install with native extensions just fine, it didn’t work right when makeing the extensions by hand.
- Open the “Start Command Prompt With Ruby” in your Start menu program group for Ruby
- In that new prompt, load the DevKit vars:
- Go to the makefile:
- Run the config: