In a Ruby file, when I press command-R to run, about half the time I get an error indicating that we tried to compile as an Xcode project and we are not an Xcode project. Why is TextMate doing this and how can I prevent it? The language thingy at the bottom says it's Ruby so clearly someone in there knows it is; it just doesn't seem to be the same guy who responds to command-R. Thx. m.
Probably because you have the Xcode bundle enabled. If you open up the bundle editor you can filter out the xcode bundle. Or if you use the Xcode bundle change the scope of the "Build & Run" command to the appropriate scope. Check out Chapter 13 of the manual for instructions on setting scopes.
In situations like this one, I find it very useful to: Type command+control+T Click on the magnifying glass and change the setting to key equivalent Type the offending key command.
On Jan 28, 2008 5:03 PM, Matt Neuburg matt@tidbits.com wrote:
In a Ruby file, when I press command-R to run, about half the time I get an error indicating that we tried to compile as an Xcode project and we are not an Xcode project. Why is TextMate doing this and how can I prevent it? The language thingy at the bottom says it's Ruby so clearly someone in there knows it is; it just doesn't seem to be the same guy who responds to command-R. Thx. m.
-- matt neuburg, phd = matt@tidbits.com, http://www.tidbits.com/matt/ A fool + a tool + an autorelease pool = cool! One of the 2007 MacTech Top 25: http://tinyurl.com/2rh4pf AppleScript: the Definitive Guide - Second Edition! http://www.amazon.com/gp/product/0596102119
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Try manually going up to Bundles > Ruby > Run to make sure that it is indeed performing the correct command-R hotkey. If this manual selection shows the XCode error then your Ruby bundle command has probably changed. You can check that by going through the following:
1) If you open up the Bundle Editor: ctrl-alt-command-B or Bundles > Bundle Editor > Show Bundle Editor
2) In the top left the select list should have "Show All" then in the list expand Ruby and click Run and tell us what is in the right pane.
3) Make sure the scope (bottom right) looks something like: source.ruby - source.ruby.embedded
4) Tell us what the script in the right textarea has.
- Joe P
On Jan 28, 2008, at 8: 03PM, Matt Neuburg wrote:
In a Ruby file, when I press command-R to run, about half the time I get an error indicating that we tried to compile as an Xcode project and we are not an Xcode project. Why is TextMate doing this and how can I prevent it? The language thingy at the bottom says it's Ruby so clearly someone in there knows it is; it just doesn't seem to be the same guy who responds to command-R. Thx. m.
-- matt neuburg, phd = matt@tidbits.com, http://www.tidbits.com/matt/ A fool + a tool + an autorelease pool = cool! One of the 2007 MacTech Top 25: http://tinyurl.com/2rh4pf AppleScript: the Definitive Guide - Second Edition! http://www.amazon.com/gp/product/0596102119
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
I've noticed this happening if the cursor is inside a string interpolation, e.g. if the cursor was between 'do' and 'stuff': foo = "bar_#{do.stuff}_baz"
I just have to remember to move the cursor out of such a place before hitting CMD+R
On 29 Jan 2008, at 04:38, jeff emminger wrote:
I've noticed this happening if the cursor is inside a string interpolation, e.g. if the cursor was between 'do' and 'stuff': foo = "bar_#{do.stuff}_baz"
I just have to remember to move the cursor out of such a place before hitting CMD+R
For the records, we plan to fix this :)
-
Allan Odgaard -
jeff emminger -
Joseph Pecoraro -
Matt Neuburg -
Peter Cowan