On 7. Apr 2007, at 11:41, Florian Gilcher wrote:

[...] But I do have some other strange behaviour regarding ruby versions, hinting that there is something wrong with Textmates handling of ruby versions.

It does not consistently use TM_RUBY, as it can’t e.g. use it in shebang lines

If you need it to use a custom installed version the only proper way is really to setup your PATH to point at the custom version before the standard version: http://macromates.com/textmate/manual/ shell_commands#search_path

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

My .bash_login reads (no .bash_profile or .profile in ~):

export PATH="/usr/local/bin:/usr/local/sbin:/opt/local/bin:/usr/local/mysql/bin:$PATH"

# Setting PATH for MacPython 2.5 # The orginal version is saved in .bash_login.pysave PATH="/Library/Frameworks/Python.framework/Versions/Current/bin:${PATH}" export PATH

which should lead to using /usr/local/bin/ruby , my ruby 1.8.4 installation. To make the problem more exciting, the command uses the shebang line:

#!/usr/bin/env ruby

This one points to ruby 1.8.4, too:

Nostalgia-For-Infinity:~ skade$ /usr/bin/env ruby -v ruby 1.8.4 (2005-12-24) [i686-darwin8.6.1]

Digging further, i modified the command 'Validate Syntax':

#!/usr/bin/env ruby require ENV['TM_SUPPORT_PATH'] + '/lib/textmate' puts "using ruby-" + RUBY_VERSION.to_s result = `"${TM_RUBY:=ruby}" -wc 2>&1` puts result TextMate.go_to :line => $1 if result =~ /-:(\d+):/

And changed `"${TM_RUBY:=ruby}" -wc 2>&1` to `"${TM_RUBY:=ruby}" -v´. Running the Command now yields:

using ruby-1.8.2 ruby 1.8.4 (2005-12-24) [i686-darwin8.6.1]

Perhaps i missed something, but i do feel like it doesn't honor the PATH correctly.

On the other hand: version is edge with newest bundles - nothing is perfect.

Meilleures salutations Florian

Allan Odgaard wrote:

On 7. Apr 2007, at 11:41, Florian Gilcher wrote:

...

[...] But I do have some other strange behaviour regarding ruby versions, hinting that there is something wrong with Textmates handling of ruby versions.

It does not consistently use TM_RUBY, as it can’t e.g. use it in shebang lines

If you need it to use a custom installed version the only proper way is really to setup your PATH to point at the custom version before the standard version: http://macromates.com/textmate/manual/shell_commands#search_path

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

*hmm*

Yes, I did that, but forgot to mention it. But I _also_ forgot to log out after doing this.

Thanks for showing the obvious Florian

P.S.: Fortunately, I'm not one of those RTFM-guys. Otherwise, this would have been my nemesis.

Allan Odgaard wrote:

On 7. Apr 2007, at 13:30, Florian Gilcher wrote:

...

[...] Perhaps i missed something, but i do feel like it doesn't honor the PATH correctly.

Please see the paragraph marked “important” near the bottom at http://macromates.com/textmate/manual/shell_commands#search_path

The PATH you setup for bash is NOT the PATH variable given to GUI programs in general.

Le 7 avr. 07 à 15:58, Yvon Thoraval a écrit :

nevertheless, ill try-out the .bash_profile given.

that works ! even without restarting a new session nor restarting TextMate itself.

with the simplest content of .bash_profile :

[ -f /etc/profile ] && . /etc/profile [ -f ~/.bashrc ] && . ~/.bashrc

export PATH="$HOME/bin:/opt/local/bin:$PATH"

thanks to all !

Yvon

Hello TextMate users,

...

and i usually use shebang like that :

#! /usr/bin/env ruby -wx

Just FYI, it makes no sense to pass Ruby's -x switch in a shebang line.

It might not always be the best idea to pass any arguments at all in the shebang line, not ever operating system can handle this.

Patrick

Le 7 avr. 07 à 17:24, James Edward Gray II a écrit :

Just FYI, it makes no sense to pass Ruby's -x switch in a shebang line. It will never have any effect there, unless you follow it up with a directory name.

fine thanks to let me know that point, i have to say this is more an habit to put that x, i don't know what it means exactly )))

best,

Yvon