Removing the BundleIndex.binary did the trick.
I didn’t understand the first instruction. Got to Semantic Class, but wasn’t sure where to enter Save. But it doesn’t matter as it’s working. I saw little harm in removing the file since this was a new install, although I’d copied over my TextMate folder from Application Support in setting up M1 MBP from 2013 MBP. I didn’t let Apple migrate much of anything except my iCloud.
PS: The gear menu doesn’t much look like a gear. I assume this is Apple’s doing.
I’ll do a reboot now just to confirm all is good. Well I already know it isn’t because I’m having a Ruby gems issue, but I’ll leave that for another post if I don’t sort it out.
On Oct 30, 2021, at 4:44 AM, Allan Odgaard via TextMate firstname.lastname@example.org wrote:
On 29 Oct 2021, at 18:38, Greg via TextMate wrote:
But if I save a Ruby file, it’s as if Cmd-A, Cmd-X is run first. Cmd-Z brings it all back. Doesn’t matter whether I use Cmd-S or File>Save
Most likely you have a broken command running on callback.document.will/did-save. With a ruby file open use ⌃⌘T and switch to “Semantic Class” via the gear menu and then enter “save” to see if anything is being run on save.
Broken here could be a problem with the command source, the bundle item, or perhaps the bundle index, the latter can be rebuilt by first removing it and relaunching TextMate:
rm ~/Library/Caches/com.macromates.TextMate/BundlesIndex.binary _______________________________________________ TextMate mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org