Text editor "SaveAs…" broken -- replaces original file as well

"Save As…" was removed from the standard File menu items long ago but I used this http://osxdaily.com/2012/08/27/enable-save-as-os-x-mountain-lion/ to restore it an equally long time ago. That shortcut addition recently stopped working properly. It creates the new file but also replaces the original file. Well poo…


I removed the keyboard shortcut and discovered that if I open the file menu, hold down Option to turn Duplicate into Save As… that it STILL works improperly. It seems something within the OS changed and buggered how Save As… works no matter what.


Does anyone know how to make Save As… work again? Please don't reply if your answer is to use Duplicate. That's not an answer as Duplicate is a misguided multi-step replacement of the simple and easy Save As… function.

Mac mini (Late 2012), OS X Yosemite (10.10.3)

Posted on Aug 26, 2016 7:33 AM

Reply
15 replies

Aug 26, 2016 8:15 AM in response to actionmarker

It was helpful that you posted an example of the Save dialog. It made me try something and make a discovery. The "Keep changes…" option DOES appear if I do Save As… of a rich text doc. It does not appear when saving a plain text doc.


The docs I'm modifying are all plain text because they end up being imported to a Google spreadsheet as CSV files. Rich text gets into issues of smart quotes and such that really muck up the process. So now the question becomes why doesn't the "Keep changes…" option appear in the save dialog?

Aug 26, 2016 10:52 AM in response to dialabrain

Well, now I'm more baffled than ever. When I started this topic NOTHING I did would get the "Keep changes…" option to appear other than changing the file type. Mind you, I was experimenting with existing files so, obviously, they had already been saved. Every edit (without file type change) and Save As… resulted in the both the new and old files having the same edited info. At no time was there any option to keep changes.


I created the test file for screen cap purposes, saved it, tried to Save As… (same failure), changed it rtf, did Save As… with Keep changes and now Keep changes appears on ALL save dialogs. WT*? I even restored the removed app keyboard shortcut so Save As… appears on the file menu. Keep changes still appears and works.


I don't understand and certainly can't explain it. I've been doing the exact same daily creation/edit of text files for at least 4 years without the problem I originally reported. I can't recall ever having the Keep changes option in the past -- at least not since the ill-advised removal of the standard Save As… function.


Thanks for nudges that made me test things in different ways but I sure wish I knew why the dialog box changed.

Aug 26, 2016 1:59 PM in response to TheCheezWhiz

There are two ways to get things back the way you want them for TextEdit. The first fixes all OS X apps, and those written by Apple not included with the OS (such as Final Cut X).


Step one: Open the System Preferences and click on the General tab. By default, two options are off. Turn on the check boxes for Ask to keep changes when closing documents, and Close windows when quitting an application.


User uploaded file


The first is particularly important to Save As since you do not want Autosave/Versions saving anything without your consent. If you don't check the first box, your original document will receive the same changes as your Save As document, defeating the entire purpose of not having your original assume all of the same changes. The second isn't necessary to Save As, but if you're like me, you also have no desire for your desktop Mac to behave like an iPad, which restores all apps back to their last state on a startup or restart whether you want it to or not.


Step two: Related to the Close windows when quitting an application check box is reopening windows when logging back in. Again, it's an iPad like behavior, which many desktop users also didn't like. Select Restart or Shut Down from the Apple menu and uncheck the box for Reopen windows when logging back in. You can then click Cancel. Your change to the check box will be saved.


User uploaded file


Your Mac will now work like any Mac before Lion, 10.7. Apps will not launch themselves and program windows will not restore themselves on a restart or power on.


Step three: Back to Save As. Open the System Preferences and click on Keyboard. Choose Application Shortcuts in the left column. By default, the only item there is Show Help menu. You're going to add a new one. Click the + button. Where it says Menu Title, type Save As and stop. Be sure to capitalize each word. Do not put a space after "as". Three periods does not work here. You must enter a true ellipses. On a U.S. keyboard, that's Option+; (Option key plus the semi-colon).


User uploaded file


Where it says Keyboard Shortcut, press Command+Shift+S. Click the Add button and close the System Preferences. Your screen should look like the image below.


User uploaded file


Close any applications you may have had open and relaunch them. Save As… will now replace Duplicate in all menus where Command+Shift+S would be. Duplicate will remain in your menus, but now has no keystroke (on the desktop, Command+D will be Duplicate, as it always has been). Save As will also work as you've always used it. After saving your document with a new name, you can close the original and it will do so without asking if your want to save your changes to the original. Even better, the original closes without any of the changes applied to it. And by having the check box on for Ask to keep changes when closing documents, you can close a document that has changes without Autosave/Versions saving those changes without asking. You will instead get a choice of Revert Changes, which will have the same effect as the old Don't Save.


If you search around, you'll find Terminal commands to completely disable Autosave/Versions globally. Don't do that. If you do, then even with the above changes, Save As… will disappear from Preview. The only commands in the menu to save any file will be Save or Export. The Terminal command doesn't affect TextEdit the same way, Save As… stays in the menu. I don't have any of the iLife or iWork apps, so I don't know how it would affect those. From those reporting who have tried these steps, Save As… returns to Command+Shift+S. It doesn't matter that Autosave/Versions is active at this point. With the changes above, your Mac will essentially behave like OS X in Snow Leopard or earlier. Not that Autosave/Versions working in the background still won't slow your system down when working with large files, but at this time, you can't have it both ways.


*********************************************************************


That takes care of Save As… globally. If you'd like to take it a step further (I do on all versions of OS X after Snow Leopard), is to replace the version of TextEdit that comes with Lion and later with the SL version.


1) Create a folder named Applications in your user account.


2) Copy TextEdit from Snow Leopard into this new folder.


3) Use Terminal to delete the version of TextEdit that comes with Lion or later from the root Applications folder. You can also open the Get Info dialogue on it and change all permissions to Read/Write. You may also need to add yourself (the admin user) as an account in TextEdit with permissions. Give yourself Read/Write access. Then you can put the newer version of TextEdit in the trash from the desktop without the OS telling you it's "required".


Since a version of TextEdit will still exist (in your user account), there's no need to change file associations. The reason for putting it in your user account is permissions. If you were to put it in the normal Applications folder, doing a Repair Permissions in Lion or later will destroy SL's versions of TextEdit, and you'll have to retrieve it from SL again. Repair Permissions doesn't do anything to user accounts, so it will remain untouched there. The SL version of TextEdit has no idea what versions or autosave is, so will behave as you're used to. That is, saving changes only when you tell it to.

Aug 26, 2016 1:58 PM in response to Kurt Lang

Thank you for the detailed response. All of the Save As… settings had already been done but I went back through them just to be absolutely sure. I even had the shortcut properly setup using an ellipsis rather than 3 periods. Everything was just as you detailed except I haven't replaced Text Edit.


What's ironic is I used to do Windoze support and it's not uncommon to run through the same steps repeatedly before the reaching the proper outcome. (Win can be amazingly like Einstein's definition of insanity: doing the same thing over and over again and expecting different results.) I just don't think of trying that with macOS. That said, something mysterious returned the Save As… function to working properly.

Aug 26, 2016 2:16 PM in response to TheCheezWhiz

That said, something mysterious returned the Save As… function to working properly.

Adding the Save As… shortcut in the keyboard preferences overrides Duplicate, which was assigned to the same keystroke as the default.


Combined with that, turning on the check box for Ask to keep changes when closing documents causes the OS to do two things:


1) Ask what to do when closing a document without having first pressed Save, or Save As. Just like the Mac OS always did before Lion. It prevents the OS from saving as yet unsaved changes without asking what you want to do.


2) Automatically causes the OS to close the original document without applying any unsaved changes to it when doing a Save As. Only the new file has the changes. This again is the pre-Lion behavior of the Mac OS all the way back to the first Macintosh OS, and what long time Apple users expect the OS to do.


With these options/changes implemented, you don't have to replace TextEdit with an older version. Save As will do what you expect, and the OS will ask what to do when closing a file with unsaved changes. I just like replacing it because I prefer a version of TextEdit that doesn't even know what Autosave or Versions is.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Text editor "SaveAs…" broken -- replaces original file as well

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.