TextMate has ruby version (1.9.3) configured but bundle action still uses ruby system version (1.8.7)
Hello,
I'm using the SCSS bundle and I'm tryingrun an action but I get this error :
*/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems.rb:777:in `report_activate_error': Could not find RubyGem sass (>= 0) (Gem::LoadError) from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems.rb:211:in `activate' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems.rb:1056:in `gem' from /usr/bin/sass-convert:18*
I installed the sass gem only for ruby 1.9.3 so I configured TextMate to use the 1.9.3 version (using TM_RUBY) but the SCSS bundle keeps using the system version of ruby which does not have the sass gem installed.
I don't know what to do next.
Thanks for your help.
-- View this message in context: http://textmate.1073791.n5.nabble.com/TextMate-has-ruby-version-1-9-3-config... Sent from the textmate users mailing list archive at Nabble.com.
On Jun 11, 2013, at 22:03, aliezer aliwam07@yahoo.fr wrote:
[…] I installed the sass gem only for ruby 1.9.3 so I configured TextMate to use the 1.9.3 version (using TM_RUBY) but the SCSS bundle keeps using the system version of ruby which does not have the sass gem installed.
The TM_RUBY variable is only for the ruby which should be used for user scripts, e.g. Run and Validate Syntax.
Looking at the bundle, majority of the commands call ‘sass-convert’ (not ruby).
Is your installed sass-convert working when called from a terminal?
I believe that the shebang of the sass-convert script uses an absolute path to locate ruby, and if you installed it for ruby 1.9.3 then the shebang should call ruby 1.9.3, in a terminal you can check this using:
which sass-convert && head -n1 $(which sass-convert)
If you need further help, please provide the output from above execution and let me know exactly what command (in the SCSS bundle) that is failing for you. Also, I assume you’ve installed the SCSS bundle via Preferences → Bundles.
Thank you for your answer.
All the convert to sass or css or scss bundle actions fail with the same error mentioned above.
When executing the command to check the shebang, I get this : /Users/alilalouch/.rvm/gems/ruby-1.9.3-p429/bin/sass-convert #!/usr/bin/env ruby_noexec_wrapper
As a workaround, I installed sass for the ruby system version, the bundle actions now works.
If you have a fix or if I did something wrong, please let me know.
-- View this message in context: http://textmate.1073791.n5.nabble.com/TextMate-has-ruby-version-1-9-3-config... Sent from the textmate users mailing list archive at Nabble.com.
On Jun 14, 2013, at 21:22, aliezer aliwam07@yahoo.fr wrote:
[…] When executing the command to check the shebang, I get this : /Users/alilalouch/.rvm/gems/ruby-1.9.3-p429/bin/sass-convert #!/usr/bin/env ruby_noexec_wrapper
As a workaround, I installed sass for the ruby system version, the bundle actions now works.
If you have a fix or if I did something wrong, please let me know.
I think installing for 1.8 is the best workaround. The rvm version has a shebang that’ll use first ruby found via PATH, but does not work with the system ruby. In contrast, the sass-convert installed via /usr/bin/gem has a shebang that explicitly points to the system’s own ruby (1.8).
Since sass-convert was installed explicitly for ruby-1.9.3-p429 it probably should point directly to this ruby in its shebang, though this would be a question for the rvm/gem maintainers.
-
aliezer -
Allan Odgaard