----- Original Message ----- > From: Josef Latt <[email protected]> > To: [email protected] > Cc: > Sent: Friday, 16 March 2012 5:31 PM > Subject: Re: Report a bug > > Hi, > > Am 15.03.2012 23:29, schrieb Rob Weir: >> On Thu, Mar 15, 2012 at 4:28 PM, Hagar > Delest<[email protected]> wrote: >>> >>> <snip> >> > But I think we know how >> to solve, or at least reduce problem #2. The trick is to reduce the >> "window of vulnerability" for total loss by saving initially to a >> temporary file, and only after the file is completely saved then >> rename it. Since an OS-level rename operation is lighting fast, you >> reduce your risk. And if power does go out during the rename >> operation, modern OS's will know enough to rollback the file names so >> you still have your temporary file in place. Then the app can check >> for any temporary files when it loads and offer to restore them. > > Whats about the implemented 'AutoRecovery information'. It saves all > information to recover files after a crash. AFAIK these information will > be deleted after the files are completely saved. > IMHO its needful to set the recovery time shorter than default. > > AFAIK, the automatic backup was replaced by this function. > > Josef > > -- > PGP Schlüssel: 311D1055 > http://keyserver.pgp.com >
Auto-recovery needs to be fixed. Since starting to use the software about 6 years ago I have read more than a few complaints about the 'recovery' process over-writing the saved version of the file with something less than the saved version if not a corrupted version of the file Terry > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
