On Thursday 21 March 2013 19:02:13 David Faure wrote:
I'm afraid it's one or the other:
* safe code, always a working file available, but hardlinks get splitted up
* possibility to corrupt the existing file, but a backup exists; hardlinks
are kept.
OK, bug number 2, saving into a
On Thursday 21 March 2013 19:02:13 David Faure wrote:
I'm afraid it's one or the other:
* safe code, always a working file available, but hardlinks get
splitted up
* possibility to corrupt the existing file, but a backup exists;
hardlinks
are kept.
OK, bug number 2, saving into a
On Sunday, 24. March 2013 16:25:20 Christoph Cullmann wrote:
On Thursday 21 March 2013 19:02:13 David Faure wrote:
I'm afraid it's one or the other:
* safe code, always a working file available, but hardlinks get
splitted up
* possibility to corrupt the existing file, but a backup
On Sunday 10 March 2013 16:03:06 Dominik Haumann wrote:
Hi k-c-d / kwrite-devel,
Kate uses KSaveFile in KDE 4.10 to avoid data loss during save operations.
According to [1] KSaveFile will be deprecated in favor of QSaveFile with
kf5/Qt5.1.
Unfortunately, using KSaveFile introduces quite
Hi David,
since you pushed QSaveFile to Qt5.1, can you comment on this?
Thanks!
Dominik
On Sunday, March 10, 2013 16:03:06 Dominik Haumann wrote:
Hi k-c-d / kwrite-devel,
Kate uses KSaveFile in KDE 4.10 to avoid data loss during save operations.
According to [1] KSaveFile will be
Hi k-c-d / kwrite-devel,
Kate uses KSaveFile in KDE 4.10 to avoid data loss during save operations.
According to [1] KSaveFile will be deprecated in favor of QSaveFile with
kf5/Qt5.1.
Unfortunately, using KSaveFile introduces quite some regressions in Kate:
1. KSaveFile: Kate/kwrite makes a
