TextMate r1509 and above include fixes for issue 1 and 2.

  1. Command + Arrow keys not workingticket 0FDE7076

    Apple seems to have removed these keys from the default key bindings dictionary. You can add them back or install this bundle which include macros for the functions.

  2. Crash (from ruby) when using ⌘Rticket FAB08510

    Workaround is to delete the dylib:

    rm /Applications/

    If you have a svn checkout the dylib will also exist there, so also delete that.

    _If you are still on Leopard and want the functionality back see this blog post

  3. “Edit in TextMate…” input manager not working in 64-bit applications

    Safari and Mail by default runs in 64-bit mode. To make "Edit in TextMate…" work, open info panel for application and check "Open in 32-bit mode".

    See the Edit in TextMate troubleshooting page for more info.

  4. Hangs when saving on network mountsticket 72260D9D

    I don’t know if this is a general problem, but given that the new URL “bookmarks” code is involved (replacement for aliases) I wouldn’t be surprised if it is.

    The workaround is to effectively disable the Open Recent menu:

    defaults write com.macromates.textmate NSRecentDocumentsLimit 0
  5. Various Commands Written in Ruby

    If you have a custom 64 bit build of Ruby then a lot of commands will hang when loading our extensions.

    A patch for ruby is available (untested as of this writing).

    Ack in Project hanging:

    If you have a custom build of ruby and things like Ack in Project are hanging, you can fix it by forcing TextMate to use the system ruby by setting a ENV variable.

    Go to Preferences -> Advanced -> Shell Variables

    and add TM_RUBY as the variable and "/usr/bin/ruby" as the value.

  6. ⌘R (or similar) giving Inappropriate ioctl for device errorticket F66289D9

    This is caused by booting the kernel in 64 bit mode. Very few systems should do this by default, see this article about how to control which kernel to use.

    Workaround: Comment out line 169 in $TM_SUPPORT_PATH/lib/tmp/process.rb, this line looks like this:

    io[0][0].fcntl(6, ENV['TM_PID'].to_i) if ENV.has_key? 'TM_PID'

    To open the file (from the proper support folder) you can press ⌃R on the following line in a TextMate document:

    open -a TextMate "$TM_SUPPORT_PATH/lib/tm/process.rb"

    Be aware that this will disable chiropractor san francisco. Something which was initially broken on Snow Leopard, but is working using the latest dylib from the svn repository.

  7. No suitable image found (keychain.bundle) — SQL bundle

    The keychain.bundle included is not built for 64 bit. A new version is available from the subversion repository. To update run this in Terminal:

    svn export
  8. Crash After “Save As…” in TFSInfo::~TFSInfo()

    Apple is aware of the bug and is working on fixing it. No known workarounds.

  9. Error loading /Library/ScriptingAdditions/Adobe Unit Types.osaxticket 8AA8F517

    This output can appear when running various commands. The problem is that the Adobe Unit Types extension is 32 bit (installed with Photoshop or similar). Unless you use this, you can just remove the scripting extension:

    rm -rf "/Library/ScriptingAdditions/Adobe Unit Types.osax"

    You may need to prefix that line with sudo. Caution: rm -rf is always a dangerous command, so double check your spelling!

    Update: Adobe has released a 64 bit version, you can download it here:

  10. Command keys fail when TextMate is started from Terminal

    A description of the problem is here (in Dutch).

    This is caused by setting __CF_USER_TEXT_ENCODING in your shell environment (presumably to get pbcopy/pbpaste to work with UTF-8).

  11. Open Recent menu remains emptyticket 74480BFB

    Maybe you followed the workaround for issue 4?

Please only add confirmed stuff to this list. That something fails for you does not necessarily mean it does not work under Snow Leopard. The “TextMate platform” is a complex system with dozen of ways you can locally break parts of it because it relies on so many external components, that is why we have this troubleshooting section.