I’d assumed this was a problem with TextMate flakiness, so starting afresh would fix things, right? Nope. I deleted the app configuration with AppCleaner and downloaded a fresh copy of TextMate from GitHub. Whatever caused this was keeping schtum.īlow away the app config and start from scratch. Unfortunately, I could see literally nothing being logged when I tried to save files. The “Console output” in the error message refers to Console.app, the log viewer that can be found in the Utilities folder. I still don’t fully understand what caused the problem, but this is what I tried to fix it: If so, here’s a quick write-up of what I tried for the next person to run into it. A trawl of Google suggests that I’m the only person who’s ever hit this error. Actually, it decided that ⌘+S should do nothing, and trying to click “Save” in the File menu would throw this error dialog. Two days ago, TextMate on my laptop decided it didn’t fancy saving files any more. For example, I expect that my text editor should be able to open, edit, and save files. People in glass houses, etc.īut I do have some basic expectations of the software I use. A trawl through the code I’ve written would reveal many embarrassing or annoying bugs. I write software for a living, and writing bug-free software is hard. I try not to make unreasonable complaints about the quality of software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |