Auto-save of Untitled saves to /tmp, which is volatile

[Stephan Sokolow]

The auto-save functionality uses /tmp as its storage location for documents which haven't been given a filename yet, but many distros (mine included) wipe /tmp on startup. (This meets FHS requirements) This is bad for situations like power outages.

Data which should be preserved across reboots, power loss, system crashes, and the like is supposed to go into /var/tmp.

[Gergely Janossy (marcabru)]

"The auto-save functionality uses /tmp as its storage location for documents which haven't been given a filename yet"

In my version (pyroom 0.3.2) also for documents with name! E.g. If I save a document as ~/proba.txt , and kill pyroom, there is an autosaved file left in: /tmp/proba.txt_tmp_YE2zAP, and no recovery takes place when I restart pyroom. In fact I did not now where my file is, only from this bugreport.

WOuldn't it a be a better solution if you save the document in the same folder (for untitled files, in the ~), and recovered automatically upon restart?

[Florian Heinle (tiax)]

Hi,

you're right. Your solution makes more sense than the current way of automatic saving. Gedit etc do it the same way.

We'll implement this.

[Florian Heinle (tiax)]

Hi,

I'm currently rewriting the autosave mechanism to address this issue

[Florian Heinle (tiax)]

fixed in revno:141

[Florian Heinle (tiax)]

fixed in 0.4 release