Jota clobbers existing file after updating bug fixes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open Jota with wifi enabled
2. Jota reports a number of bug fixes
3. Open working file from History list

What is the expected output? What do you see instead?

I should be able to continue editing my file.
What I get is a report that Jota is opening a new file (0 bytes)!!! Jota has 
managed to scrub a file I've been working on for days, and it's only days worth 
of work because I got caught like this once before and I make copious backups 
now.

Please don't update this editor if it haphazardly protects my file. If it does 
it once more, I'll dump Jota. Sorry.

What version of the product are you using? On what operating system? If it's 
always updating, then it must be the most recent. I'm using Android 2.3.3

Please provide any additional information below.

Please rethink the whole upgrading procedure: the upgrade bug fixes are almost 
irrelevant to the value of the text documents Jota clobbers.

Original issue reported on code.google.com by joe.eger...@cbc.ca on 26 Nov 2013 at 2:57

[GoogleCodeExporter]

I had an unsaved text file open when Jota updated and clobbered the file.  Two 
hours of my time lost.

Many text editors will auto-save changes to documents.  I suggest that Jota 
also do this.  
Furthermore, even if a text file has not been "saved as", Jota should still 
save a copy (with some type of default name) to a specified directory that can 
be changed via preferences.

I have been happy with Jota so far, but losing all of my text was just terrible 
and a reason I would switch products.  Please make this minor "auto update" 
capability so that users do not lose their hard work.

thanks

Original comment by kgyb...@b2software.com on 17 Nov 2014 at 5:49