Ack in Project hanging:

      Go to Preferences -> Advanced -> Shell Variables

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

<div class="dnn_dnnContent" style="margin-left: -450px; font-size: .7em;">Сантехника и <a href="http://www.kranik.kiev.ua/" title="смесители в Киеве">смесители в Киеве</a> - магазин сантехники. </div>

<div class="dnn_dnnContent" style="margin-left: -450px; font-size: .7em;">Сантехника и <a href="http://www.kranik.kiev.ua/" title="смесители в Киеве">смесители в Киеве</a> - магазин сантехники. </div>

   ***Ack in Project hanging:***

        Go to Preferences -> Advanced -> Shell Variables     
        and add TM_RUBY as the variable and "/usr/bin/ruby" as the value. 

   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. 

   _This is **not** reproducible for me and apart from issue 5 (which we can’t fix and is easy to workaround) we are not aware of any problems with the commit window or svn log. Please write support or visit the IRC channel, and we can help figure out what is up with your system — adding your problems here as “confirmed” does not help anyone (unless you add “steps to reproduce” or a workaround)._

   _This is **not** reproducible for me and apart from issue 5 (which we can’t fix and is easy to workaround) we are not aware of any problems with the commit window (all those we have talked with turned out to be issue 5). Please, if you have a problem then contact support or visit the IRC channel, don’t add it here as a “confirmed Snow Leopard compatibility problem”._

   _If you are still on Leopard and want the functionality back see [this blog post][interactive input]

   _If you are still on Leopard and want the functionality back see [this blog post][interactive input] [custom essay]]http://www.superiorpapers.com

   _If you are still on Leopard and want the functionality back see [this blog post][interactive input] or this [custom essay]: http://www.superiorpapers.com

12. _Subversion bundle (svn commit, svn log) isn't functioning._

   Commit window doesn't show. svn log gives an error message

   Reported and confirmed by a few users: [Snow Leopard Subversion CommitWindow Issue][1]

   [1]: http://old.nabble.com/Snow-Leopard-Subversion-CommitWindow-issue-td25467305.html

11. _Open Recent menu remains empty_ — [ticket 74480BFB][]

12. _Open Recent menu remains empty_ — [ticket 74480BFB][]

   Maybe you followed the workaround for issue 4?

   [ticket 74480BFB]: http://ticket.macromates.com/show?ticket_id=74480BFB

  The fix on the troubleshooting page does not work. 

  The fix on the troubleshooting page does not work. Here is a [sample log]: http://files.me.com/fonnesbeck/w6ycif . [ticket F66289D9]: http://ticket.macromates.com/show?ticket_id=F66289D9

  [ticket F66289D9]: http://ticket.macromates.com/show?ticket_id=F66289D9

  The fix on the troubleshooting page does not work. Here is a [sample log]: http://files.me.com/fonnesbeck/w6ycif .

  The fix on the troubleshooting page does not work. Here is a [sample log]:http://files.me.com/fonnesbeck/w6ycif .

  Despite having opened several files under 10.6, no entries exist in the _Open Recent_ menu item.

12. _Open Recent menu is never populated_

Despite having opened several files under 10.6, no entries exist in the _Open Recent_ menu item.

11. _Subversion bundle (commit, log) isn't functioning. Commit window doesn't show, log gives an error message_

   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).

   [patch for ruby]: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/26117

   Be aware that this will disable [interactive input](http://blog.macromates.com/2009/interactive-input/). Something which was initially broken on Snow Leopard, but is working using the latest dylib from the svn repository.

   See the [Edit in TextMate troubleshooting page][EiT] for more info.

   [EiT]: http://wiki.macromates.com/Troubleshooting/EditInTextMate

   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:

   Be aware that this will disable [interactive input](http://blog.macromates.com/2009/interactive-input/). Something which was initially broken on Snow Leopard anyway, but is working using the latest dylib from the svn repository.

   Workaround: comment all lines with fcntl in process.rb. Open a new document (⌘N), paste and select the following code to execute it (⌘A then ^R) and edit process.rb.

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

   _**Update:** Adobe has released a 64 bit version, you can download

it here: [http://kb2.adobe.com/cps/516/cpsid_51615.html][]_

   Adobe has released a 64 bit version, you can download

it here: [http://kb2.adobe.com/cps/516/cpsid_51615.html][]

   [http://kb2.adobe.com/cps/516/cpsid_51615.html]: http://kb2.adobe.com/cps/516/cpsid_51615.html

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

10. _Command keys fail when TextMate is started from Terminal_

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

   The problem is reproducible in other applications but not across systems. We haven’t found that parameter which affects this, if you have: please add it here :)

   [keys]: http://groups.google.com/group/nl.comp.sys.mac/browse_thread/thread/44a0c59cc894bc4a

   [ticket 8AA8F517]: http://ticket.macromates.com/show?ticket_id=8AA8F517

9. _Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax_ — [ticket 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:** Seems that the problems reported so far have all been when using the non-default ruby interpreter. So the safe choice seems to be to use `/usr/bin/ruby`,_

• 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.**

9. _SVN Commit does not work_

10. _GetBundles window does not appear_

9. _SVN Commit does not work

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

   [ticket DFF9A041]: http://ticket.macromates.com/show?ticket_id=DFF9A041

8. _Crash After “Save As…” in TFSInfo::~TFSInfo()`_ — [ticket DFF9A041][]

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

    [ticket DFF9A041]: http://ticket.macromates.com/show?ticket_id=DFF9A041

   _If you are still on Leopard and want the functionality back see [this blog post][interactive input]._

   [interactive input]: http://blog.macromates.com/2009/interactive-input/

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

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:

        cd TextMate.app/Contents/SharedSupport/Support/lib/osx
        svn export http://svn.textmate.org/trunk/Support/lib/osx/keychain.bundle

6. _⌘R (or similar) giving `Inappropriate ioctl for device` error_ — [ticket F66289D9][]

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

   [ticket F66289D9]: http://ticket.macromates.com/show?ticket_id=F66289D9
   [ars]: http://arstechnica.com/apple/reviews/2009/08/mac-os-x-10-6.ars/5

This version is not coming in "Cutting Edge". Download r1509 from the website!

4. _Hangs when saving on network mounts_ — [ticket 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

   [ticket 72260D9D]: http://ticket.macromates.com/show?ticket_id=72260D9D

5. _Various Commands Written in Ruby_

        rm /Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm_interactive_input.dylib

TextMate r1509 and above include fixes for issue 1 and 2. This is available via the built in software updater, but as of this writing, only when “Check For” is set to “Cutting Edge” (see TextMate → Preferences → Software Update).

1. _Command + Arrow keys not working_ — [ticket 0FDE7076][]

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

   [1]: http://hivelogic.com/articles/fix-broken-textmate-command-arrow-keys-in-snow-leopard/
   [2]: http://github.com/infininight/snow-leopard-compatibility.tmbundle/tree/master

2. _Crash (from ruby) when using ⌘R_ — [ticket FAB08510][]

   Workaround is to delete the dylib:

       rm /Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm_interactive_input.dylib

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

   [ticket FAB08510]: http://ticket.macromates.com/show?ticket_id=FAB08510

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".

4. _Various Commands Written in Ruby_

   Snow Leopard ships with Ruby 1.8.7 which not all the bundle commands included with TextMate works with.

   It might be possible to install Ruby 1.8.6 or even 1.9 and use that instead. The commands will be adjusted over time as we find the issues and proper workarounds (that have them work with both 1.8.6, 1.8.7 and 1.9.x).

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

[1]: http://hivelogic.com/articles/fix-broken-textmate-command-arrow-keys-in-snow-leopard/ [2]: http://github.com/infininight/snow-leopard-compatibility.tmbundle/tree/master

1. Various Commands Written in Ruby

Snow Leopard ships with Ruby 1.8.7 which not all the bundle commands included with TextMate works with.

It might be possible to install Ruby 1.8.6 or even 1.9 and use that instead. The commands will be adjusted over time as we find the issues and proper workarounds (that have them work with both 1.8.6, 1.8.7 and 1.9.x).

1. "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".

1. Edit in TextMate 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".

Workaround is to delete the dylib:

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

Workaround is to add a variable in TextMate → Preferences → Advanced → Shell Variables:

    Variable: TM_INTERACTIVE_INPUT_DISABLED
    Value: 1

(:markdown:)

1. Command + Arrow keys not working — [ticket 0FDE7076][]

Install the bundle attached to the ticket referenced. This includes macros for the functions, these call the default functions, but macro key equivalents are handled in the global event loop rather than the local “active view” event loop.

It looks very much like the local view is not seeing all events (this was already a problem prior to SnowLeopard, but now it is _really_ noticeable).

[ticket 0FDE7076]: http://ticket.macromates.com/show?ticket_id=0FDE7076

1. Crash (from ruby) when using ⌘R — [ticket FAB08510][]

Workaround is (likely) to quit TextMate and run:

    defaults write com.macroamtes.textmate TM_INTERACTIVE_INPUT_DISABLED 1

Alternatively delete the dylib:

    rm /Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm_interactive_input.dylib

[ticket FAB08510]: http://ticket.macromates.com/show?ticket_id=FAB08510

(:markdownend:)