TextMate Runner Bug in 64bit Snow Leopard

When running the 64bit kernel in Snow Leopard, TextMate will fail to execute most scripts.

This produces the following error for me (in the case of a Ruby script):

/Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm/process.rb:169:in `fcntl': Inappropriate ioctl for device (Errno::ENOTTY) from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm/process.rb:169:in `run' from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm/executor.rb:211:in `parse_version' from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm/executor.rb:98:in `run' from /Applications/TextMate.app/Contents/SharedSupport/Bundles/Ruby.tmbundle/Support/RubyMate/run_script.rb:93

I was able to "fix" it by commenting out line 169 in:

/Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm/process.rb

I haven't noticed any adverse affects (yet).

Posted by chrisp Fri, 20 Nov 2009 06:45:00 GMT


The TextMate Beachball Revisited

I posted one way to get rid of the TextMate beachball earlier. It just keeps coming back though. My current project is heavy on themes, meaning I have a lot of cache and images in a theme directory that also contains views and stylesheets that I need to edit. This really began to slow things down for me, and there’s no way to remove subfolders from the project. I finally figured out a way to put the beachball to rest for good though (hopefully).

First follow my previous advice and create a brand new TextMate project and add all folders that contain files that you will edit (and no others). Don’t add the log or tmp directories. Be thorough though - don’t leave out folders that MIGHT contain editable files in the future either.

TextMate will automatically scan all of these folders for filesystem changes, but there is a way to tell it NOT to scan certain subfolders. To do this you select the top-level folder that contains subfolders that don’t need editing (usually image and large static content areas). Right click and select the “Show information” option.

The “Folder pattern” textbox contains a regular expression that filters out unwanted folders. All you need to do is add the name of the folder(s) you want left out. Just add it to the existing list of names that are | separated. Make sure you have a single | on both ends of the folder’s name. You don’t have to put the entire path, just the name.

For example, I don’t want to check image subfolders, so I change this: !./(.[^/]|CVS|_dar to this: !./(.[^/]|images|CVS|_dar

Now my massive images folder is hidden. After doing this for all applicable folders, TextMate is faster than ever! Plus I still get the benefits of the live filesystem check that other methods don’t have.

Posted by chrisp Tue, 30 Jan 2007 23:33:00 GMT


TextMate + BeachBall = Snore

Getting delays while working in TextMate from the beach ball of death?

If you only add files and directories that you work on in a project, this is greatly minimized. Also make sure that you don’t have the log directory in your textmate project. TextMate scans the filesystem for changes, and the log directory is always doing that (slowing things down).

If you are using an existing project (or not), create a new one then:

Go to your rails path in finder and open TextMate and choose File -> New Project

Drag over only the directories that you will need to edit. Avoid log and tmp, since there is nothing to edit there. You may want to avoid public if there are no html files in it that need editing (sometimes it contains a lot of images).

Save the project using “Save As” Overwrite the original if necessary.. Save doesn’t pick these changes up for some reason.

This should reduce the size of the project and make that alt+tab magic nice and speedy.

Posted by chrisp Tue, 21 Nov 2006 21:25:00 GMT