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

List:       kwrite-devel
Subject:    [Bug 76942] file saving, consider vi like save to new file, unlink old,
From:       "Casteyde.Christian" <casteyde.christian () free ! fr>
Date:       2005-12-21 18:32:26
Message-ID: 20051221183226.31765.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=76942         




------- Additional Comments From casteyde.christian free fr  2005-12-21 19:32 -------
Well, in your use case, you're right. In fact it depends on the semantic you give to \
hard link: alias of a filename (and therefore modifying it should modify the \
underlying file), or a tool to save space (and a copy on write should be done on \
save). As I always use symlinks anyway, and as being two time slower and more risky \
(due to more disk space use while the saving process) is really annoying, I won't \
fight on such a conceptual question.

Your solution is probably the right one for most people, and is very safe (I don't \
consider vi as the safest program either, so I don't care the fact it doesn't destroy \
hardlinks either). _______________________________________________
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]