Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Save as in TextEdit?

I'm in TextEdit and I want to do a Save As... command but there isn't a Save As.. command. I see Save a Version command but nothing happens when I select that.


Why is this so difficult?

Thank you

Posted on Sep 6, 2012 1:50 PM

Reply
Question marked as Best reply

Posted on Sep 6, 2012 2:40 PM

Well, I just read your page (thank you, again) and I'm implementing the workflow as designed and I think having to select Duplicate and then Save..., versus just selecting Save As..., is less efficient. That is my opinion, and I am welcome to have it. 😉


The Auto Save is really irrelevant to this discussion of not having Save As. I can have both.


The Save Version command is also irrelevant to Save As... I can create a version of the document I'm working in, but what if I want a new document based on the content of the current one? Save As...


I have document A and I want to have another document, document B, and have it based on document A, but with some different content. The fastest way to accomplish that, in my opinion, and the method I've been using for over 20 years, is to select Save As. I select Save As, I type in the name of document B, and then I start working in it. I have Document A and Document B on the hard drive and I'm working in the one I want to work in, which is Document B.


I don't really see how selecting Duplicate and then Save... is a better method. If Apple wants to add Duplicate to their File menu, more power to them, but I don't see how losing a feature is beneficial to me.


How is losing the Save As... command a good thing?


Now, you say I'm not well informed. What am I missing here?

47 replies

Jan 20, 2015 6:33 AM in response to Mykl

Yes, pretty much everyone knows that.


When you have years of muscle memory set to Command+Shift+S, it's greatly annoying to have the keystroke move. Try Command+Shift+S and then Command+Option+Shift+S - both with one hand. The first is very easy to do and I can hit those keys without even looking at the keyboard. The "new" way can't be done. I've tried shifting my left hand every which way, and you can't perform that keystroke with one hand.


Apple was long a proponent of the "Human Interface" rules. There's a reason opening a file is always Command+O, closing an item is Command+W, etc. They idea is for uniformity so you don't have to think about the most commonly used commands. The desktop and your apps all behave the same way, which speeds up your workflow by not having to memorize different commands for the same thing every time you use a different app. Then Apple suddenly decides not to follow its own rules and breaks over two decades of interface function.


Apple was deluged with angry users about this change (and others) in Lion. Mountain brought back a way to revert Save As to Command+Shift+S. It can all be done in the System Preferences. No need for lengthy Terminal commands or other under-the-hood tricks. It isn't documented, though. You either have to discover it yourself, or look up the solution online.

Jun 4, 2015 10:50 AM in response to GlennCarmichael

Did they ever fix this issue in the latest OS and go back to the more Mac-intuitive "save as"? (I'm still on Mavericks) I still screw up every time trying to figure out how to "duplicate". The easiest solution is to simply command-d the file in the finder and then edit that one.


I'm also wondering if Apple wasn't doing this to gauge how people would respond to them eliminating "save as" and replacing it with "duplicate" for all programs in future OS'...

Jun 4, 2015 11:12 AM in response to Kurt Triffet

Kurt Triffet wrote:


Did they ever fix this issue in the latest OS and go back to the more Mac-intuitive "save as"? (I'm still on Mavericks) I still screw up every time trying to figure out how to "duplicate". The easiest solution is to simply command-d the file in the finder and then edit that one.


I'm also wondering if Apple wasn't doing this to gauge how people would respond to them eliminating "save as" and replacing it with "duplicate" for all programs in future OS'...


No, Yosemite still has the same behavior. 😟


I noticed that Pages and Numbers have the same idiotic "feature".

You have to Duplicate first, then Save it versus just selecting Save As.

Jun 4, 2015 11:28 AM in response to Scot Walker

If you follow the steps in the link I posted, you can make Mountain Lion through Mavericks behave the same as Snow Leopard and earlier. Autosave/Versions will still be active, but Save As… will be where you expect it in all apps, and the original file will not have the same changes as the Save As… file up to the point you create the offshoot.

Jun 4, 2015 11:35 AM in response to Kurt Lang

Thanks, Kurt - helpful but would be so much easier to see it back in the menu.
It's unfortunate that with every new OS or virtually any major software program, there is always a tradeoff between gaining something in one area, and losing something important in another. :-)


TextEdit is no longer the wonderful simple program it used to be, too many added steps to do simple things just so they could load it with more features - some many don't even want or need. I often use it as a repository for cutting and pasting text between programs like Word and Adobe AI or ID so that formatting gets stripped, and it's quite cumbersome now.


The last version in Snow Leopard was probably TextEdit's pinnacle.

Jun 4, 2015 11:39 AM in response to Kurt Triffet

Thanks, Kurt - helpful but would be so much easier to see it back in the menu.

That's the whole point of the outline. Save As… returns to its traditional spot in the menus of all apps and works with the normal Command+Shift+S keystroke instead of having to add the Option key.

TextEdit is no longer the wonderful simple program it used to be,

You can change that, too. It's what I do on every Mac we use.


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. 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.

Nov 13, 2015 9:41 AM in response to Kurt Lang

Terminal.app If you are comfortable using Terminal.app, you can add a different keyboard shortcut this with one simple line. First, quit all your apps except Finder and Terminal. Then paste this command (as one line) into Terminal.app (and press Return):


defaults write -globalDomain NSUserKeyEquivalents -dict-add 'Save As...' '@$S'


view rawdwrite-global-saveas.sh hosted with ❤ by GitHub

That's it!

Jan 7, 2016 1:18 PM in response to Razorhog

Exactly how I feel. Drives me crazy. All I want is a standard text editor with standard features. First I had to hunt around to just save in plain text. Then, instead of the universal "Save as" we now have "Duplicate" and unless you look for help or read the documentation, the method for saving as via "Duplicate" is unclear at best. Apple seems to insist on being different whether it's useful to be different or not. Standardization is actually useful for human interfaces.

Save as in TextEdit?

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