Just to follow up, it seems that this may be related to my .tm_properties file. I have

  projectDirectory = "${TM_FILEPATH/(\/Users\/jon\/Development\/Git\/[^\/]+).*/$1/}"
  windowTitle = "${projectDirectory/^.*\/([^\/]+)$/$1/} — $TM_DISPLAYNAME"

in the directory above the ones I was testing in.

Within those testing directories, TextMate takes up 100% CPU *for each tab I open*, until it uses all four of my cores (with four tabs). And commands don't work (possibly because of the high CPU usage, I guess). But when I move that .tm_properties file away, everything seems to go back to normal. If I put it back, the problem recurs.

I hope this helps pin down the issue.

Jon


On 13 February 2013 11:18, Jon Clayden <jon.clayden@gmail.com> wrote:
Thanks, Allan, for the response, but moving these two folders elsewhere (and then reinstalling the bundles I use, via TM prefs, but no customisations) does not solve the problem. I haven't made any recent changes to any bundle, and as I mentioned, downgrading was previously effective at solving the issue. I'm on Mountain Lion (10.8.2), if that's relevant.

Regards,
Jon



On 13 February 2013 09:20, Allan Odgaard <mailinglist@textmate.org> wrote:
On Feb 12, 2013, at 12:17 PM, Jon Clayden <jon.clayden@gmail.com> wrote:

> I have suddenly experienced wholesale failure of commands in recent builds of TextMate 2 […]
> […]
> I don't really know where to start with figuring this out, so some help would be appreciated!

You may have uninstalled the Bundle Support bundle or another central bundle.

To revert to defaults you can remove the ~/Library/Application Support/TextMate and  ~/Library/Application Support/Avian folders (though this also removes potential customizations done to the bundles).


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