On Sun, 2010-06-20 at 03:29 +0200, Branko Vukelic wrote:
> On Sat, Jun 19, 2010 at 10:44 PM, Sven Neumann <s...@gimp.org> wrote:
> > Hi,
> >> Also I was really surprised that an auto backup isn't in GIMP already. I
> >> used
> >> to use a really old, backwoods photo editor and it automatically made a
> >> backup
> >> file and autosaved it every ten minutes.
> > What you really need for your case is not an auto-backup feature, but
> > atomic save operations. Instead of writing over the existing file when
> > you save, GIMP should write to a temporary file in the target directory.
> > And only if it succeeds in writing this file completely should it move
> > the temporary file over the existing file. That way you wouldn't have
> > lost your file completely.
> > Please feel free to open a bug report for this.
> Better way would be to do what most text editors do. Create a backup
> of the old file (remember those files that end with a tilde '~'?)
> before overwriting it with the new save. It should be a trivial fix.
It is actually a very difficult fix. There are hundreds of save plug-ins
and all would have to be fixed. Also GIMP plug-ins may save using a
helper plug-in that transparently enables saving to remote locations. It
is definitely not trivial to fix this.
Gimp-user mailing list