3 ms·
Do you not find use cases where you do -not- want the document saving? I spend a lot of time editing code that is being served by a local development server, a
by scarecrowbob 13y ago
Do you not find use cases where you do -not- want the document saving?
I spend a lot of time editing code that is being served by a local development server, and much of the time I do not want my changes saved until they are a complete set simply because I don't need it to start feeding me a bunch of errors from half-finished code.
Similarly, there are a lot of times when I will open a document, modify or reformat part of its contents in preparation for copying them somewhere else with different requirements, and then close the document without saving it.
So aren't there any times in your workflows where you don't want the files saved unless you explicitly want to commit some changes?
- dragonwriter 13y agoNot really, though (and this relates to the first of your examples) I do what persisting (avoid loss) changes made distinct from committing (identifying as in a done/stable/ready-for-some-use-besides-continued-editing state) changes.