https://bugs.documentfoundation.org/show_bug.cgi?id=156954
Bug ID: 156954
Summary: implement robust data recovery for lost work (autosave
on interval, etc.)
Product: LibreOffice
Version: 7.5.5.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: medium
Component: framework
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: libreoff...@caseyconnor.org
I have "save autorecovery info" set to 2 minutes, and "always create backup
copy", and File-Versions->"Always save a new version on closing" enabled, but
it is still too easy to lose work by accidentally deleting sections and not
noticing, or by accidentally clicking "don't save" in the dialog that appears
when you close a document, especially when you have multiple documents open,
especially if your window manager places Save/Don't Save dialogs in the wrong
place, etc.
It seems like File->Versions->"Always save a new version on closing" does not
save a version when closing if the user does not decide to save changes at the
closing dialog. (I filed bug #156953 for that). If that bug is fixed (or I am
mistaken), it would help a lot with this.
Another potential option would be something like "[x] keep autorecovery
information on document close even if crash doesn't happen" and to allow
autorecovery to be manually instigated at any time (as long as you do it before
the next autorecovery save happens, I suppose)
But it would be nice to have more robust mechanisms for recovering older
versions of files, lost data, etc.
Specifically, an "autosave" function... here's the deluxe dream version for me:
[x] automatically save backup copies every X minutes
[ ] save backups in same directory as original
[ ] prune backup copies in original directory to
[ ] maximum age of ______ days/hours/minutes
[ ] minimum number of backup files to keep: _____
[ ] maximum number of files: ____
[ ] maximum total disk usage of backups of a given file (minimum one
backup): _____
[x] use this centralized directory for all autosave copies: ________
[x] prune backup copies in centralized directory to
[x] maximum age of ______ days/hours/minutes
[x] minimum number of backup files to keep: _3___
[ ] maximum number of files: ____
[ ] maximum total disk usage of backups directory (minimum one backup):
_____
[x] also save a backup copy when manually saving
[x] save a backup copy on exit, whether or not changes are saved on exit
[x] attempt to save a backup copy when program crashes
...this is distinct from autorecovery as these copies are accessible whether or
not the program crashes, they persist (according to settings), and they are
always available.
This could also incorporate the timestamp and file metadata ideas in bug
#154109.
I know there are million things to consider about it (filename collisions, UX
details to work out, etc.) It just feels frustrating that in this day and age
we should still be able to so easily lose data, especially when editing a
little 10k text file.
Thanks for considering!
--
You are receiving this mail because:
You are the assignee for the bug.
