2 ms·
The workflow I've always used: Open file > Save with new filename > Change new file > Save changes 10.7/10.8 just removes the last step. The only people h
by zdw 14y ago
The workflow I've always used:
Open file > Save with new filename > Change new file > Save changes
10.7/10.8 just removes the last step. The only people having issues are those that confuse the middle two steps.
Or, in unix parlance, you cp then vi. Not the other way around.
- _delirium 14y agoIn vi, though, what I usually do is open a file first, and then if I want to 'save as', I do ':w newfile'. I don't have to decide before I open the file if I want to duplicate it or not, and it would be very unexpected behavior for ':w newfile' to also modify the original file.
- deleted 14y ago[deleted]
- zmmmmm 14y agoOften I don't know that I'm going to want to save as a new version until half way through. I some times open the original intending to make minor, non-destructive, changes, then end up making bigger changes and think "hmm, I'd better save as a different file in case I need the old one later". I think to advance to the world of auto-save, one also needs to much more visibly advance to the world of file versioning where it's really clear to the user whether their changes are ultimately destructive or not.