I *think* it's because tabs are both "a tab" (the UI thing) and "a file" (the proxy thingie in normal title bars). So when you click one, if you slightly misclick, you can drag the tab "over" the text view. As it is considered "a file" by the text view, TM tries to calculate an insertion point, which races with the grammar/syntax coloring that's going on (remember, you've just brought this tab to the front by click). Then you loose the runloop because something raised inside the modal drag loop, and you have to force quit.

Regards,

Etienne Samson

Le 18 sept. 2019 à 20:25, Curt Sellmer <sellmerfud@gmail.com> a écrit :

I am using the latest 2.0 release of Textmate on a 2017 Macbook Pro. MacOS 10.14.6

I have experienced this only twice in the last two days.
Both times, I had three open documents in Textmate and with the project drawer visible.

I clicked in the Tab bar to select a different document. And the program becomes unresponsive. I cannot type any characters and clicking on any part of the editor view in Textmate has no effect.

Clicking on Tabs has not effect Clicking in the File Browser has no effect.
Interestingly, dragging a Tab to the desktop will make a copy of the Document on the desktop.

Clicking on the "Menus" at the bottom of the window such as Tabs, or Language, or the GoTo menu will show the menu. Clicking on an item in the Goto Menu does not move the editor that that location.

If I switch to another app I cannot use Cmd-Tab to bring TextMate to the front. The TextMate icons is visible when I press Cmd-Tab but selecting it has not effect.
I can bring TextMate to the front by clicking on it.

Activity Monitor shows that TextMate is not using any CPU.

I have to Force Quit TextMate.

_______________________________________________
TextMate mailing list
TextMate@lists.macromates.com
https://lists.macromates.com/listinfo/textmate