Delete temporary files after saving a database

[adessec]

JabRef version 3.3 on Linux 3.16.7-35-default (openSuSE 13.2)

Steps to reproduce:

1. Activate autosave.
2. Autosave files not wriiten into the same directory as the *.bib file but to /tmp.
3. Even after saving, autosave files persist.

[adessec]

I don't think this behaviour is an enhancement but rather a bug. A version of a database that has been edited is written to /tmp every five minutes by default as long as you don't save it to the working directory. Quite annoying if it's large.

[Siedlerchr]

@adessec When it's always the same temp file that is updated than it is totally okay and totally consistent behavior.
However, it would be nice to configure the autosave to the working directoy.

[adessec]

Unfortunately it is not always the same temp file - they just multiply. At the moment, I have one small +-JF...tmp, one small jabref...tmp, one large jabref...tmp, and nine large jabref...save.bib. Nothing has been updated.

[tobiasdiez]

According to the help

The autosave file will be deleted whenever you actively save the database, and if you quit JabRef normally.

So if this does not work, then it is indeed a bug. Moreover, according to the same help page, the auto save file should actually be named $file$ (so extra dollar signs) and be put in the same folder (and I get same expression reading the code).

Moreover, I can't find anything in the code which would suggest that a file is written to a /tmp folder...

[tobiasdiez]

Ok, I think I found the problem. Should be fixed with #1277.

[adessec]

Thank you for fixing this.

[simonharrer]

Thank you for reporting the bug and helping JabRef.

PS: Donations keep us going. ;-) http://www.jabref.org/#donations