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

List:       kde-bugs-dist
Subject:    [Bug 79698] Disabling backups (file~) explicite,
From:       Marcin Kasperski <Marcin.Kasperski () softax ! com ! pl>
Date:       2005-04-07 13:47:44
Message-ID: 20050407134744.31388.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=79698         




------- Additional Comments From Marcin.Kasperski softax com pl  2005-04-07 15:47 \
------- One more comment: in my opinion there is absolutely no need to mix two things \
discussed above: a) temporary backup file made by editor while saving
b) persistent backup file left for the user in case he would like to revert to the \
pre-save file version

For instance I have read in the comment 2 that "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." It seems to me that it would be far better \
                idea to save this way:
- create temporary file
- write to this file
- when the write is succesfully done, swap it with the main file (rename original to \
                tempname, rename temp to correct name, remove previous original)
- in case of errors purge the temporary
There is small chance of error happening just while renaming the files, but the \
chances are very small, this is very simple operation. If you are paranoid, you can \
copy old orignal to the 'official' backup location, whatever it is

Nevertheless, whatever temporary backup is needed by editor while saving, there is no \
need to make it visible for the user.

Regarding 'persistent backup' - backup left for the user in case he or she woudl like \
to revert - I think, that in fact it is currently just unnecessary. We usually save \
often and we usually have unlimited or at least deep undo stack. In case of logical \
mistake, instead of looking to ~-file, it is easier and more natural to just undo \
until the expected version is met. As some people could get used to using ~-files, \
there can be option to use them but it seems absolutely unnecessary to pollute \
everybodys working space with never-being-used-files.


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