On Mar 9, 2005, at 9:48 PM, Eric Ocean wrote:
Now, Add to Repository fails with:
/bin/bash: line 11: ruby: command not found
This is probably the BASH_ENV problem. We should fail more gracefully and support TM_RUBY, but -- currently -- we don't.
Date: January 27, 2005 4:38:47 AM PST From: cryo@cyanite.org Subject: Re: [TxMt] ruby not found error To: textmate@lists.macromates.com Reply-To: textmate@lists.macromates.com
On 27. jan 2005, at 13:15, David Casal wrote:
Hello all,
Stupid question here...I have:
ruby /Users/dc/Documents/txt/scripts/todo2log.rb $TM_FILEPATH
It can't locate ruby _here_.. doesn't matter if the shebang is right later on (it's not even used). Most likely your ruby-path is setup in ~/.bash_profile, which is not sourced by TM. A solution that should fix everything path-related:
Make a file in your home-dir, say .bash_env and have it contain: source /etc/profile source ~/.bash_profile
Then set TM's BASH_ENV variable to: ~/.bash_env
That should source all relevant path stuff.
A completely different solution is of course to call the script directly: /Users/dc/Documents/txt/scripts/todo2log.rb $TM_FILEPATH ..it needs to be +x of course, for this to work.
Thanks to Torsten Becker and Chris Thomas, I was able to get things working.
The BASH_ENV trick didn't help until I created and set TM's SHLVL variable to 1 (after reading a (cryptic) tip from Allan). I hope this helps someone else.
Best, Eric
On Mar 9, 2005, at 10:52 PM, Chris Thomas wrote:
Make a file in your home-dir, say .bash_env and have it contain: source /etc/profile source ~/.bash_profile
Then set TM's BASH_ENV variable to: ~/.bash_env
On Mar 10, 2005, at 8:10, Eric Ocean wrote:
The BASH_ENV trick didn't help until I created and set TM's SHLVL variable to 1 (after reading a (cryptic) tip from Allan). I hope this helps someone else.
Yes, this stuff is a bit cryptic ;) in b6 I'll force the variables to have their correct values if defaults doesn't exist, which should hopefully solve any future problems.