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