#274 Auto-save

[Jon Jackson]

I think an auto-save feature might be helpful. On a
similar tack, I've lost 5 or 10 minutes of work a
couple of times as a result of an
ArrayOutOfBoundsException (see bug 1529211 - no big
deal, just to illustrate the point!). For this kind of
situation it would be helpful to have something to
catch any uncaught exceptions, and save the current
database to a backup/recovery file before exiting and
sending the exception to stdout. At present jabref
crashes irrecoverably with an uncaught runtime exception.

[Mark Hancock]

Logged In: YES
user_id=1167486

I think better than having a backup/recovery file, it should
automatically update the bib file when changed. As long as
undo works sufficiently, there's no reason to not just
always save. That way, we don't have to rely on exceptions
to be caught when the system *really* crashes. The mental
model here is "add to database" not "add to temporary storage".

[Jon Jackson]

Logged In: YES
user_id=1474902

I like the idea of automatically updating the bib file so
long as the last user saved version is kept as a backup.
Should the user be asked if they want to keep the changes
when they quit jabref?