Hi, I used macports to install ruby 1.9 (because my rubygems fell off the map when I installed fxruby >.<)
$which ruby1.9 /opt/local/bin/ruby1.9
$which gem1.9 /opt/local/bin/gem1.9
But I'm pretty sure my Ruby bundle is still using 1.8, Is there a relatively pain-free way to switch it over?
On Sun, Feb 14, 2010 at 9:58 PM, Josh Cheek josh.cheek@gmail.com wrote:
Hi, I used macports to install ruby 1.9 (because my rubygems fell off the map when I installed fxruby >.<)
$which ruby1.9 /opt/local/bin/ruby1.9
$which gem1.9 /opt/local/bin/gem1.9
But I'm pretty sure my Ruby bundle is still using 1.8, Is there a relatively pain-free way to switch it over?
Hi, it's not clear as to why you switched to Ruby 1.9. In any case, do you plan to make it your primary Ruby version? If this is the case, I would recommend one of the following options:
a) Install Ruby 1.9 via MacPorts using the following:
sudo port install ruby19 +c_api_docs +nosuffix
b) Install Ruby 1.9 via Ruby Version Manager
1) install RVM
mkdir -p ~/.rvm/src/ && cd ~/.rvm/src && rm -rf ./rvm/ && git clone git://github.com/wayneeseguin/rvm.git && cd rvm && ./install
2) install Ruby 1.9
rvm install 1.9.1
For more information about RVM, I would recommend referencing the following website:
Good luck,
-Conrad
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
I installed RVM, and it seems to be working (pretty cool, actually! I have 1.8.6 1.8.7 and 1.9.1 now)
Also verified that TextMate shows the correct version (though it has to be restarted if I switch).
...I think I may check out MacRuby, it's been looking interesting to me for a while!
Thanks, Conrad --Josh
Hmm, it seems that if I run TextMate from the command line, then it finds the correct version, but if I run it from Applications folder, Spotlight, or Quicksilver, then it always pulls up the the system version (1.8.6)
Is there an easy way to remedy this? If not, I can just always run it from the command line.
Tested with the code
RUBY_VERSION # => 1.8.6
And running the file with control+command+shift+e to get the tag to update.
On Mon, Feb 15, 2010 at 12:31 AM, Josh Cheek josh.cheek@gmail.com wrote:
Hmm, it seems that if I run TextMate from the command line, then it finds the correct version, but if I run it from Applications folder, Spotlight, or Quicksilver, then it always pulls up the the system version (1.8.6)
Is there an easy way to remedy this? If not, I can just always run it from the command line.
Tested with the code
RUBY_VERSION # => 1.8.6
And running the file with control+command+shift+e to get the tag to update.
You need to recheck your configuration and make sure that the RVM configuration lines are at the bottom of your shell initialization file (i.e. .profile, .bashrc, or other).
Good luck,
-Conrad
_______________________________________________
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 15/02/2010, at 7:31 PM, Josh Cheek wrote:
Hmm, it seems that if I run TextMate from the command line, then it finds the correct version, but if I run it from Applications folder, Spotlight, or Quicksilver, then it always pulls up the the system version (1.8.6)
Is there an easy way to remedy this? If not, I can just always run it from the command line.
Have a look at this blog post: http://justaddwater.dk/2009/03/10/textmate-path-modification-ruby-version-is...
Make sure your that you set PATH in TextMate's Preferences (Advanced -> Shell Variables) to reflect what you have in Terminal.app. You can also try setting TM_RUBY to the full path of the version of Ruby that you wish to use.
Good luck!
On Mon, Feb 15, 2010 at 12:51 AM, Adam Sharp adsharp@me.com wrote:
On 15/02/2010, at 7:31 PM, Josh Cheek wrote:
Hmm, it seems that if I run TextMate from the command line, then it finds
the
correct version, but if I run it from Applications folder, Spotlight, or
Quicksilver,
then it always pulls up the the system version (1.8.6)
Is there an easy way to remedy this? If not, I can just always run it
from the
command line.
Have a look at this blog post:
http://justaddwater.dk/2009/03/10/textmate-path-modification-ruby-version-is...
Make sure your that you set PATH in TextMate's Preferences (Advanced -> Shell Variables) to reflect what you have in Terminal.app. You can also try setting TM_RUBY to the full path of the version of Ruby that you wish to use.
Good luck!
-- Adam Sharp Email: adsharp@me.com Web: www.adam-sharp.net
@Adam - Josh wants Textmate to reference the correct Ruby version when he switches it on the command line using RVM. Thus, he doesn't want to hard-code any particular version.
@Josh - I'm able to access the correct Ruby version from the command as well as the Dock. Thus, try moving Textmate to the Dock.
-Conrad
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 15 Feb 2010, at 10:32, Conrad Taylor wrote:
@Adam - Josh wants Textmate to reference the correct Ruby version when he switches it on the command line using RVM. Thus, he doesn't want to hard-code any particular version.
There is two ways to set which ruby TextMate should use. Setting PATH as has already been mentioned, or setting TM_RUBY to the exact binary, e.g. /usr/bin/ruby.
I believe there is a version of RVM which maintains a symlink to the “current” ruby, so one should set TM_RUBY to that symlink, or alternatively, let PATH include the directory of this symlink.
Thanks, everyone. I found this page http://rheimbuch.posterous.com/rvm-and-textmate which explains how to setup the symlink and the TM_RUBY variable, It works pretty nicely.
On the FAQ for rvm ( http://rvm.beginrescueend.com/faq/ ), I also found where they talk about how to set it up, and go around modifying files. I did the modifications, but if it got me something better than that first link, I couldn't tell, so I took them back out (they made me a little nervous).
Anyway, that first link seems to have resolved the last of my issues, so I appreciate the help.
-Josh
On 16 Feb 2010, at 11:12, Josh Cheek wrote:
[...] On the FAQ for rvm ( http://rvm.beginrescueend.com/faq/ ), I also found where they talk about how to set it up, and go around modifying files. I did the modifications, but if it got me something better than that first link, I couldn't tell, so I took them back out (they made me a little nervous).
Good call, those instructions are EXTREMELY BAD! Someone did write them to ask for removal as not only is this a fix, you may end up breaking lots of unrelated stuff that use the ruby process library.
-
Adam Sharp -
Allan Odgaard -
Conrad Taylor -
Josh Cheek