[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: More default questions...
From:       Dominik Haumann <dhdev () gmx ! de>
Date:       2007-10-01 17:33:26
Message-ID: 200710011933.26820.dhdev () gmx ! de
[Download RAW message or body]

On Monday 01 October 2007, Andreas Pakulat wrote:
> On 01.10.07 07:51:37, Christoph Cullmann wrote:
> > On Sunday 30 September 2007 22:18, Dominik Haumann wrote:
> > > On Sunday 30 September 2007, Leo Savernik wrote:
> > > > Am Sonntag, 30. September 2007 schrieb Adam Treat:
> > > > > Another feature that I know annoys many people is the 'Backup on
> > > > > Save' feature.  I don't know a single person who uses this.
> > > > >  Maybe there are some people who use it so I don't advocate
> > > > > getting rid of it, but it really should be off by default.  Can
> > > > > you imagine using Kate as a programmers editor only to see your
> > > > > filesystem absolutely *littered* with ~foo files.
> > > >
> > > > Yes! Please, off! Off! Off!
> > > >
> > > > mfg
> > > >       Leo
> > > >
> > > > PS: Just make a backup by default if Kate crashes.
> > >
> > > I don't quite get this. If kate crashes during save, your data is or
> > > can be lost. in kde 3.5.7 kate is really stable. it wasn't that
> > > stable all the time. ths is kde4, i wouldn't be surprised if crashes
> > > exist ;)
> >
> > Yep, and beside that, the default was "on" for ages, it makes no sense
> > to change that IMHO. People disliking that can deactivate it, but for
> > first time users, it can be useful. Only if you implement a correct
> > save algo for local files, where no data can be lost on kate crash, you
> > may deactivate that, but I am not sure, if that is possible at all :(
> > (And no, writing to new file + renaming after success is no solution,
> > you may loose group info, owner info, acls, extended attributes, ....)
>
> As has recently been pointed out on k-c-d, there's KAutoSaveFile in
> kdelibs nowadays which is meant for exactly this purpose. And as far as
> I understood the intro of that class it doesn't loose any of those
> attributes because all you do is put content into it and later put that
> content back into the original file, which doesn't change file
> attributes (you don't copy it over).

With the slight difference that Kate does not use it *bleh* ;) No app uses 
it, so it is untested, and for 4.0 will probably removed from kdelibs. we 
have 2 month left for 4.0 and noone has the plan (time?) to integrate it 
right now.

dominik
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel

[prev in list] [next in list] [prev in thread] [next in thread]