On 23 Mar 2013, at 22:34, Matt Neuburg wrote:
I have modified TextMate's PATH so that it starts like this:
/Users/mattleopard/.rbenv/bin:/Users/mattleopard/.rbenv/shims: ...
The first is so that the "rbenv" command itself is visible. The second is so that rbenv's "ruby", "rdoc", "gem" and other shims are visible.
OK, so it sounds like this might work (be aware that only 2.0 will expand $HOME and $PATH in your variable settings):
TM_RUBY = "$HOME/.rbenv/shims/ruby" TM_RI = "$HOME/.rbenv/shims/ri" PATH = "$PATH:$HOME/.rbenv/bin"
I don’t know if the last line is required (for the shims to function), but by appending to PATH we don’t eclipse any of the standard tools, so it does no harm for TextMate.
So, I'm not sure where TextMate is headed with this, but I hope it's in the direction of playing even *more* nicely with rbenv and my choice of global ruby version - not less nicely. I have a lot of functionality built upon this; obviously I don't want it to break. m.
As mentioned in my previous reply, we’ll (hopefully soon) start to hardcode the /path/to/ruby to make it robust against user alterations.