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

List:       kwrite-devel
Subject:    [Bug 79698] Disabling backups (file~) explicite,
From:       Jason Keirstead <jason () keirstead ! org>
Date:       2007-05-01 11:30:47
Message-ID: 20070501113047.27821.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=79698         




------- Additional Comments From jason keirstead org  2007-05-01 13:30 -------
Just a comment...

The second poster said that having an option to disable backups is a bad idea simply \
because "When Kate saves the file it creates a backup, then it empties the file and \
starts writing. Suppose you don't have a backup and Kate crashes when saving your \
file. Result: your work is gone!"

Correct me if I am wrong, but this seems like THE WRONG way to save files. Every app \
I have ever worked on, the app saves the file to some NEW FILE on the filesystem \
(random chars.tmp) and then when the save is complete, renames the orignal file to \
somethinkg.tmp, renames the saved file to the name of the original file, then deletes \
the something.tmp. 

This way, during no stage of the file save operation is there a chance of you losing \
your original data, since file renames are atomic operations. No need for this \
"backup file" nonsense. Why doesn't Kate behave this way?

I always thought the point of these backup files was in case you saved an edit and \
decided to roll it back - which is way I always agreed with at least having an option \
to disable them for RCS/CVS/SNV controlled files.

I have realy not seen a valid argument for disabling these files. It is not "standard \
behaviour" by the way - the standard behavior for vim is to DELETE the working copy \
of the file when it is exited normally. The working copies only remain if the app \
crashes. In all normal cases of exiting the backups are removed by default, you have \
to change options to make them stick around.

So mainly I want to agree with comment #13 - kate should not use this method for \
saving files at all. And even if it does need a working copy that copy should be \
deleted by default on normal exit. It should only remain in the case of application \
crash. _______________________________________________
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]