Mountain Lion ‘Save As’ Command Also Overwrites Original File


Save As... Or is it?
Save As... Or is it?



Remember that neat little hack to bring the Save As command back to Mountain Lion? It turns out that it’s not quite as handy as we first thought. Sure, you can now “Save As” instead of being forced to “Duplicate” the file and then save it, but Mountain Lion will not only save your changes in the new document, but write them to the original at the same time.

That’s right. If you save a copy of a document to which you have made changes, OS X 10.8 will not revert the original. Instead, it’ll just add your changes and – if you close the file – save that.

It’s not an actual disaster. Thanks to Mountain Lion’s versioning, you can revert to the previous version, but that’s not going to help when you open a document and expect it to contain one thing, and it contains another. And you’re a nerd. Imagine that a Normal does this: panic would quickly ensue.

There are some workarounds… Kinda. You can set your Mac not to save files automatically on quitting an app or closing a document, but that’s hardly ideal.

Source: Mac Performance Guide


  • Vico Prima

    Nice article, thanks for the information.
    Anna @
    sewa mobil jakarta

  • nthnm

    I haven’t upgraded to Mountain Lion yet, has Save As been taken out of all programs? Or just programs Apple has designed such as Pages, etc? Though I’ve seen a few posts, I haven’t really been paying attention to the Save As articles.

  • known_as_metro

    completely disastrous change that i would have never expected from apple a few years ago.
    to make such a confusing and counter intuitive alteration to such an important element of people’s work process, and that it would go without more of an outcry, is baffling to me.
    i suppose its time to go switch back to the real innovators, because i’m getting tired of apple shoving their forced logic down my throat