[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:       2005-01-12 12:39:05
Message-ID: 20050112123905.18519.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  2005-01-12 13:39 -------
I really dont underatand your arguments.

On January 11, 2005 11:43 pm, Philippe Rigault wrote:
>  certainly don't, option c is _very_bad_ for several reasons:
>   1. Applications that make backup files (which includes all editors)
> _always_ make them in place. It is a _standard_ that all users would
> expect. 

?? The backup would still be performed in-place. It would just not be in the 
current directory. The *location* of the in-place backup file is the main 
issue. 

> 2. It is not feasible easily in a robust way, and quickly brings many more
> problems than benefits. Consider the following scenarios: a) Backup
> directory problematic (not enough space, read-only NFS-mount), which is
> detected at _write_ time, so you do all your editing and the editor bombs
> just as you hit Save. b) ~/backups/<full path> is very inefficent. Edit a
> single file in kdepim for example, and end up creating
> $HOME/.backups/opt/build/kde/3.3.2/konstruct/kde/kdepim/work/kdepim-3.3.2/k
>mail/file. c) Modify a file path (PATH1/foo -> PATH2/foo) after its backup
> is created guarantees that files do not correspind any more to their
> backups. d) ~/backups/<full path> fails to work across many machines.
> Often, home directories are shared betwen machines (e.g NFS mount). Go edit
> a file in machine1:path/file and machine2:path/file -> name collision.

All these arguments have no weight.  There is no reason you can assume that 
the current working directory is not problematic for the same reasons - it 
could be low on space, an NFS mount, etc.

Aside from that, no one is suggeiting ~/backups or whatever be the default 
location. The suggestion is that there be an *option* for the user to put 
these files in a location other than the current working directory, where 
they are clutter. If I as the user, want kate to put my backups on ~/backups, 
that should be my perrogative. It is up to me to pick a good location, and if 
the drive is on a slow NFS drive / out of space / whatever, that is my issue.
_______________________________________________
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]