Comments
-
Greg Hurrell
What is the output of
:ruby puts RUBY_VERSION
in Vim?On the surface, it looks like you're doing everything right. (FWIW, I'm on 10.9 as well with Homebrew-installed Vim and it works without any acrobatics, so there should be some explanation for why it's not working for you.)
-
Carneiro
Hi Wincent, my RUBY_VERSION in Vim is: 1.8.7
Just updated it to the latest github version and still can't get it to work. Any ideas would be much appreciated. I'd hate to have go back to ctrl-p.
-
Carneiro
I just found out that my vim has a different ruby version to my macvim. Do you think that could be causing this issue?
vim is running ruby 2 while macvim is running 1.8.2.
-
Greg Hurrell
That absolutely sounds like the cause of the issue. Command-T and Vim must link against the exact same version of Ruby if you want things to work.
If you installed Vim with Homebrew, you should install MacVim via Homebrew as well; they'll both link against Ruby 2.0.0, so you should be able to build Command-T against 2.0.0 as well and it will work in both places.
-
Carneiro
Thank you very much.
I reinstalled macvim with brew with the following command line:
brew reinstall macvim --with-lua --override-system-vim --with-luajit --with-python3
then rebuilt command-t using ruby 2, and now everything is working again, on both vim and macvim.
-
Greg Hurrell
Status changed:
- From: new
- To: closed
Add a comment
Comments are now closed for this issue.