I don't understand the lack of understanding of the 'save-as' workflow. After working with a TextEdit file for a bit, I got an error saying, 'You don't have permission to write to the folder that the file 'test' is in.' To be honest, that kind of outweighs the usefulness of turning off autosave so if someone can find a solution for that, I'd say this hint might be more useful.] I'm not sure about these sandboxing errors. [ kirkmc adds: We know that Save As is coming back in Mountain Lion, but if you want to turn of autosave for a specific application, this is good to know. This works for other apps as well, just replace TextEdit with the name of the app, e.g.: defaults write ApplePersistence -bool no defaults write ApplePersistence -bool noIt is such a relief to have that 'Save As.' option back! Hopefully I'll be able to get something done in Lion now with a minimum of cursing.

I don't know a good fix for that (if someone does, would you mind making a comment?) To disable autosave in TextEdit.app, run the following command in Terminal: defaults write ApplePersistence -bool noThis disables autosave and versions, reenables the 'Save As' option and hot-key (Command-Shift S), and reenables Command-D as a hot key for 'Don't Save'.įor TextEdit, you'll run into sandbox-related permissions errors with this with the old style Autosave, where it attempts to place a file name 'filename (Autosaved).txt' in your working directory. The good folks at stack exchange have discovered a remedy.

It's nice that it saves things for you, but it's not nice that automatically saves things that you don't want to change permanently, or that the 'Save As.' option has disappeared. The autosave feature in OS X 10.7 has been a mixed bag.

Autosave disabled excel for mac