On Sat, Aug 03, 2013 at 08:29:06PM -0400, Michael Henry wrote: > Empirically, I can verify that the behavior has changed. On > Fedora 17, the query works: > > $ ruby -r rbconfig -e "puts RbConfig::CONFIG['ruby_version']" > 1.9.1 > > On Fedora 19, this same query prints the empty string. > > The following patch changes the Ruby version detection algorithm > to check the ``VERSION`` and ``RUBY_VERSION`` variables as used > earlier in Vim's configure script. Essentially, the query > becomes:: > > $ ruby -e "puts ((VERSION rescue RUBY_VERSION))" > 1.9.3
Notice how the version number here doesn't match the version number in the previous command? RbConfig::CONFIG['ruby_version'] reports the API version, while VERSION/RUBY_VERSION report the release version. $ ruby --version ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux] $ ruby -e 'puts ((VERSION rescue RUBY_VERSION))' 1.9.3 $ ruby -r rbconfig -e "puts RbConfig::CONFIG['ruby_version']" 1.9.1 What Vim needs to know is the API version, not the release version. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <[email protected]>
signature.asc
Description: Digital signature
