Hi all, I recently updated some Ruby settings on my computer which resulted in TM_RUBY being set to my RVM version (1.9.2). Now in some bundles (GetBundles most recently) I am getting console errors that cause the commands to crash. Stuff like this:
/Users/bmf/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:214: syntax error, unexpected keyword_end, expecting $end
I fixed one or two commands by hand (I'm newish to ruby so not intimately familiar with syntax differences between versions) but that is kind of a PITA.
So, does TextMate require a specific Ruby version? When using RVM to switch Rubies, does that require a TextMate relaunch? Trying to quickly fix this stuff so I can get back to work, thanks for your help.
Brandon
On 15 Sep 2011, at 20:53, Brandon M Fryslie wrote:
[…] does TextMate require a specific Ruby version?
TextMate commands are only guaranteed to work with 1.8.7 (or whatever ships with OS X).
But commands use the ruby from your PATH where TM_RUBY is for user scripts, script validation and such.
So it should be safe to set TM_RUBY to a different ruby.
I don’t see any use of TM_RUBY in the GetBundles (which you mention had issues) found here: http://svn.textmate.org/trunk/Review/Bundles/GetBundles.tmbundle/ — I believe an older version may have wrongly used TM_RUBY.
When using RVM to switch Rubies, does that require a TextMate relaunch?
Relaunching TextMate doesn’t change the command environment, so wouldn’t think so, but I don’t know what “using RVM to switch Rubies” conveys.
-
Allan Odgaard -
Brandon M Fryslie