<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Trigger file.save every n minutes"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=127224#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Trigger file.save every n minutes"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=127224">bug 127224</a>
from <span class="vcard"><a class="email" href="mailto:stephenboston@gmail.com" title="stephenboston@gmail.com">stephenboston@gmail.com</a>
</span></b>
<pre>Auto-recovery is not an acceptable solution for this requirement.
Consider this scenario:
- I neglect to manually save a document
- I check in the directory
- On another host I make changes to the same file -- attempting to reconstruct
the lost changes
- Back on the home host I checkout those changes
- Open the document in LO
- Auto recovery overwrites the changes
Now admittedly there are steps along the way this could have been avoided, and
many people may insist that sinners must suffer the consequences of their sins.
However other people may argue, I among them, that it is not the place of
software to play the scold.
This is a feature that many people have requested and that is persistently
denied for reasons that are not clear. On the face it seems a simple request. A
timed loop that triggers the file.save function on dirty files.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>