Vim Ruby Version 2.3.7 but expected Version 2.5.3

[kyletolle]

I have used MacVim for years and absolutely love it. Thanks in advance for the help here.

I was excited for the new release because it fixed #257, which I reported in the past. However, after upgrading to MacVim 8.1.560 (152), I'm unable to use command-t in MacVim, because the expected version of Ruby doesn't match.

I get the following error:

Vim Ruby version: 2.3.7-p456
Expected version: 2.5.3-p105

I've tried brew uninstalling macvim, setting rbenv global 2.5.3, and then brew installing macvim. This did not work.

I've seen #779 and tried setting rubydll like it recommends. In order to do so, I installed ruby through brew

brew install ruby

In order to get a libruby.2.5.dylib, which I've found in the following path:

/usr/local/Cellar/ruby/2.5.3_1/lib/libruby.2.5.dylib

And I set rubydll as follows at the top of my .vimrc:

set rubydll=/usr/local/Cellar/ruby/2.5.3_1/lib/libruby.2.5.dylib

But I keep getting the error that vim is using Ruby version 2.3.7.

Would you have any ideas as to why vim is not using Ruby version 2.5.3?

Here's some system information:
macOS: 10.14.1
Homebrew: 1.8.4
rbenv: 1.1.1
rbenv ruby: 2.5.3
system ruby: 2.3.7
brew ruby: 2.5.3

Thanks again for all your hard work!

[ychin]

It sounds more like Cmd-T is expecting 2.3.7 to me. Did you rebuild the C components? One issue with the Cmd-T plugin is that the native component + ruby does mean there's more fussing needed to get it to work.

You can always do :ruby puts RUBY_VERSION in Vim to be sure what Vim is using.

[kyletolle]

When I run :ruby puts RUBY_VERSION, I get 2.3.7.

Even when I start vim using vim -N -u NONE as mentioned in the contributing file, and run :ruby puts RUBY_VERSION, I see 2.3.7.

I built Command-T against 2.5.3, which is what it's expecting when I use it in vim, but it still seems that Vim's picking up 2.3.7 instead of the expected 2.5.3 version of Ruby. And I'm trying to specifically set the rubydll in the .vimrc, which also does not seem to work.

Sidenote: You're right that there is a lot more fussing with Command-T to get it running. Each time I upgrade MacVim, I have to recompile the native component of Command-T. It had given me lots of trouble in the past, but I had a set of commands that worked until the new version of MacVim. I might need to explore an alternative because it's getting really old having to fight this so often and it being a gamble whether I'll lose a ton of time to this with each upgrade to MacVim. But Command-T has been extremely helpful for me, which is why I've endured it so far.

[kyletolle]

I was able to compile Command-T against Ruby 2.3.7 to get that Command-T working for me, since MacVim uses Ruby 2.3.7.

Still not certain why I couldn't get MacVim to use Ruby 2.5.3, though.

The release notes say:

Script interfaces have compatibility with these versions:
…
Ruby 2.5

And this lead me to believe that I would need to have Ruby 2.5 installed in order to use MacVim, but this does not seem to be the case. Is it mentioned anywhere what version of Ruby MacVim requires?

[ychin]

Cool! Glad to see if working for you.

I'm not sure why MacVim keeps using the 2.3 library. Setting rubydll should work and you can try setting it at runtime instead of in your vimrc to see if it works.

As for the versioning, Vim is usually compiled against a particular Ruby version, so when we build MacVim we do the same thing. Since we compile with +ruby/dyn we load the library dynamically so that users who don't care about Ruby don't have to deal with it. Technically, the library you load in should match the version Vim is compiled with. See :h ruby-dynamic:

Unix ~

The 'rubydll' option can be used to specify the Ruby shared library file
instead of DYNAMIC_RUBY_DLL file what was specified at compile time. The
version of the shared library must match the Ruby version Vim was compiled
with.

That said on my machine I find that it works whether I use a 2.3 or 2.5 library, so the changes may not be big enough.

[ychin]

I'm going to close this out, since you seemed to have found a way around it. MacVim does get built with 2.5 right now so I'm not sure why you couldn't get it to work, but you could load any DLL you want using the rubydll option.

[kyletolle]

Thanks for the additional information @ychin. Running :set rubydll=/usr/local/Cellar/ruby/2.5.3_1/lib/libruby.2.5.dylib at runtime did not change the ruby version that :ruby puts RUBY_VERSION displayed, and I'm not sure what that might be related to.

But I am happy enough now that I can continue to use vim and Command-T without issue. I'll keep an eye out in the future to see if things change. I hope this issue might be of help to someone else who faced a similar issue.

[aeciolevy-ven]

I have spent some hours trying to match the version but without success...

cd ~/.vim/bundle/command-t/ruby/ext/command-t/ 
rvm use 2.3.7
ruby extconf.rb
make clean 
make

I tried to do it on the and it did not work as well..

cd ~/.vim/bundle/command-t/ 

[ychin]

@aeciolevy-ven Sorry what's the issue you are seeing? Have you tried setting rubydll?

[aeciolevy-ven]

Not yet. I have tried to match the ruby version of command-t and vim.
I am getting the same error

command-t.vim could not load the C extension.
Please see INSTALLATION and TROUBLE-SHOOTING in the help.
Vim Ruby version: 2.3.7-p456
For more information type:    :help command-t

But I already set ruby version 2.3.7 in the command-t folder.

[ychin]

MacVim is compiled against 2.5.3 as mentioned (it will be compiled against 2.6 in the upcoming release since 2.6 has been released in December 2018), so you should use that, rather than an older 2.3.7 version.

If you follow #798 (comment) and do :ruby puts RUBY_VERSION in MacVim what do you see?