3 ms·
I'm inclined to agree with Microsoft Word's autosave, here. If you are making edits to a file, the implication (which could be wrong) is you're intending to ove
by Dalewyn 3y ago
I'm inclined to agree with Microsoft Word's autosave, here. If you are making edits to a file, the implication (which could be wrong) is you're intending to overwrite at the end. And indeed, autosave came around because way too many people were losing document modifications to freak power outages and computer crashes.
If the intent is to not overwrite an existing file, I personally learned to make a copy first either via Save As in the program or by copying in whatever file manager I'm using. That way I make my intention clear to both myself and the computer.
I've actually burned myself numerous times because occasionally I would forget to copy first, instinctively hit CTRL+S frequently because I hail from before autosaving became widespread, and then realize I just overwrote something I wanted to keep as-is.
- gradstudent 3y agoAs I read it, the GP complains about Word auto-saving on top of the OG document. I think intermediate changes should go to an auto-save buffer until you tell the editor to save over the top. For that reason I'm inclined to agree with the GP. Word's behaviour is wrong and the process you describe sounds like a workaround.
- nullindividual 3y agoOffice's auto save feature only works on OneDrive and SharePoint Online, which means every change is versioned. There is no 'overwriting' the OG document. The OP can go back in the history and recover it.