Hi,
I am trying to create a foldingStopMarker for Python language as '^\s*##' but it seems to be triggered only when I don't have any space before ##. This seems to be the problem with any stop marker beginning with whitespace. Is there a way around?
TM 1589.
Thanks! Abhi
setting the textmate-ruby-variable (TM_RUBY) does not fix the issue for me!
i also tried to set the variable to /opt/local/bin/ruby
which is what i get from
$ which ruby
i installed ruby using macports removing all preinstalled (buggy) apple ruby stuff.
any ideas?
On 24 Nov 2009, at 09:01, Peter Schröder wrote:
[...] i installed ruby using macports removing all preinstalled (buggy) apple ruby stuff.
That might have been your mistake — Apple’s ruby works fine with TextMate’s Subversion bundle, yet many custom builds of ruby on Snow Leopard *does not*.
The problem has to do with loading extensions: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/26117
hi allan,
is there some other workaround i can try, or logs i can look into?
i think that using a macports ruby version is a 'standard' way of using ruby on the mac.
kind regards, peter
Am 24.11.2009 um 12:47 schrieb Allan Odgaard:
On 24 Nov 2009, at 09:01, Peter Schröder wrote:
[...] i installed ruby using macports removing all preinstalled (buggy) apple ruby stuff.
That might have been your mistake — Apple’s ruby works fine with TextMate’s Subversion bundle, yet many custom builds of ruby on Snow Leopard *does not*.
The problem has to do with loading extensions: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/26117
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Tue, Nov 24, 2009 at 6:47 AM, Allan Odgaard mailinglist@textmate.org wrote:
On 24 Nov 2009, at 09:01, Peter Schröder wrote:
[...] i installed ruby using macports removing all preinstalled (buggy) apple ruby stuff.
That might have been your mistake — Apple’s ruby works fine with TextMate’s Subversion bundle, yet many custom builds of ruby on Snow Leopard *does not*.
This is just one of the pain points for someone who is a serious ruby developer and needs to deal with multiple versions of ruby 1.8 and 1.9.
I have a project which needs 1.9, and I use rvm to manage multiple ruby implementations, If I start mate from the shell I need to make sure that I'm using the default ruby at launch or bad things happen like ctrl-shift-v to do a syntax check on a ruby file hangs textmate.
And the flipside is that this means that I can't use things like the rspec bundle to run tests inside textmate for 1.9 dependent code.
I guess it's something I just have to live with, at least for now.
On 24 Nov 2009, at 14:34, Rick DeNatale wrote:
I have a project which needs 1.9, and I use rvm to manage multiple ruby implementations, If I start mate from the shell I need to make sure that I'm using the default ruby at launch or bad things happen like ctrl-shift-v to do a syntax check on a ruby file hangs textmate.
We do what we can to ensure our commands work with most builds of ruby, but e.g. this Snow Leopard issue is really out of our hands to fix — though that should not affect ⌃⇧V which I believe should work with 1.9.
That said, if you set PATH in TextMate’s shell variables preferences you won’t have to worry about the PATH active when you use ‘mate’ (starting with r1589 we ensure TM has the default PATH set there by default, so if you upgraded, it actually should “just work” now).
And the flipside is that this means that I can't use things like the rspec bundle to run tests inside textmate for 1.9 dependent code.
You can additionally set PATH / TM_RUBY to your 1.9 version as a project specific variable for your project which require 1.9 — probably best to set TM_RUBY rather than PATH, adn ⌘R + ⌃⇧V will use that, but most other things in TM will be unaffected. Not sure if the RSpec bundle honers TM_RUBY, if not, it could probably be made to do that.
On Tue, Nov 24, 2009 at 8:52 AM, Allan Odgaard mailinglist@textmate.org wrote:
On 24 Nov 2009, at 14:34, Rick DeNatale wrote:
I have a project which needs 1.9, and I use rvm to manage multiple ruby implementations, If I start mate from the shell I need to make sure that I'm using the default ruby at launch or bad things happen like ctrl-shift-v to do a syntax check on a ruby file hangs textmate.
We do what we can to ensure our commands work with most builds of ruby, but e.g. this Snow Leopard issue is really out of our hands to fix — though that should not affect ⌃⇧V which I believe should work with 1.9.
Yes, I'm not sure what's up with the hang using 1.9
That said, if you set PATH in TextMate’s shell variables preferences you won’t have to worry about the PATH active when you use ‘mate’ (starting with r1589 we ensure TM has the default PATH set there by default, so if you upgraded, it actually should “just work” now).
Great, I did just autoupdate yesterday. Now when I run ctrl-shift-v it says is is using 1.8.7 even though I ran mate from a shell set to run Ruby 1.9.
And the flipside is that this means that I can't use things like the rspec bundle to run tests inside textmate for 1.9 dependent code.
You can additionally set PATH / TM_RUBY to your 1.9 version as a project specific variable for your project which require 1.9 — probably best to set TM_RUBY rather than PATH, adn ⌘R + ⌃⇧V will use that, but most other things in TM will be unaffected. Not sure if the RSpec bundle honers TM_RUBY, if not, it could probably be made to do that.
Mixed results here:
I set the project TM_RUBY variable to point to my ruby1.9 executable
I wrote a spec to see if the RSpec bundle runner is executing 1.9 which it is.
I can't run features with the Cucumber bundle under textmate I get this:
Running: bash "2>&1 /Users/rick/fifthrail/relevance_legalpm/script/cucumber /Users/rick/fifthrail/relevance_legalpm/features/login_by_name_or_emails.feature --format=html" bash: 2>&1 /Users/rick/fifthrail/relevance_legalpm/script/cucumber /Users/rick/fifthrail/relevance_legalpm/features/login_by_name_or_emails.feature --format=html: No such file or directory false
But that's probably a separate issue, since I get the same results if I unset the project specific variable.
Of a bit more concern, with the project variable set to use 1.9, ctrl-shift-v's pop-up says that it is using 1.8.7 to do the syntax check, and 1.9 and 1.8 syntax is different.
But on the whole it's a step forward.
On 24 Nov 2009, at 16:04, Rick DeNatale wrote:
[...] Yes, I'm not sure what's up with the hang using 1.9
Looking at the command I see it requires the textmate ruby lib, so this might load one of our extensions (which is what causes the hang).
Btw: when a command hangs, one can press ⌃C or ⌘. to break it.
[ RSpec Bundle] Mixed results here:
I set the project TM_RUBY variable to point to my ruby1.9 executable
I wrote a spec to see if the RSpec bundle runner is executing 1.9 which it is.
I can't run features with the Cucumber bundle under textmate I get this: [...] But that's probably a separate issue, since I get the same results if I unset the project specific variable.
Yeah, no idea what that is about — none of the bundles are bundles I am familiar with. Btw: be sure to grab the RSpec directly from GitHub, the one we mirrored in svn is very outdated, but also has seen some commits not in the official, which is why we have hesitated with deleting it.
Of a bit more concern, with the project variable set to use 1.9, ctrl-shift-v's pop-up says that it is using 1.8.7 to do the syntax check, and 1.9 and 1.8 syntax is different.
This is the actual command: http://pastie.textmate.org/private/crnusmhkavi0auvspuu0ua
As you can see, it uses the value of TM_RUBY (with ruby as fallback) to get version and validate your code. So my best guess: TM_RUBY is not set for the project :) Try use Bundles → Bundle Development → Show TM_* Variables.
-
Abhi L -
Allan Odgaard -
Peter Schröder -
Rick DeNatale