Package: gjots2 Version: 2.4.1-2 Severity: important Tags: upstream I just found out that the autosave function of gjots2, while neat, has some serious shortcomings in implementation.
Steps to reproduce 1) open a gjots file 2) change something, but don't save 3) close the file or quit the program I will not be asked if I want to save my changes. So, for example if I changed my mind on the changes in #2 and would like to discard them, ordinarily I would simply close the program and I'd assume to be back to my original state. Not with gjots2 anymore. The old state is preserved but the user will need to know where and most importantly be aware they need to recover back to the state in #1 manually. This is not in line with how other programs use autosave (for recovery) so this can potentially lead to data loss the next time the file is opened and autosaved.
