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

List:       kwrite-devel
Subject:    Re: [Bug 74289] New: "touch"ing a file that's open in kate causes
From:       Anders Lund <anders.lund () lund ! tdcadsl ! dk>
Date:       2004-02-05 22:36:10
Message-ID: 200402052336.29277.anders.lund () lund ! tdcadsl ! dk
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 05 February 2004 22:17, daniel quinn wrote:
> kate suddenly thinks that the file's been edited.   normally, this wouldn't
> be a problem 'cause who goes around doing that?   but i've found that if i
> have a file open when i do a "cvs commit" the files mtime is updated and
> then i have to close and click "ok" every time it complains that closing
> the file could cause me to lose data etc.

This is intended. Of cause in the case of a commit, you may feel silly, but 
for example a cvs update of the repository containing the file is a different 
situation... And even for a commit, if you have any cvs tags in the file 
(like $id$) you will need to reload the file in kate before saving it again, 
if you want to preserve those data.

You can reload files by pressing F5, which will present you with a warning.

In the future, maybe we can make this functionality a bit more intelligent - 
for example offer some means of viewing/merging the difference. However, the 
current way it is handled is the best we could come up with so far. Ideas 
will be appreicated, but they must be constructive, embracing the fact that 
we do want to warn users about files modified outside the editor.

-anders
-- 
*** NEW ID *** Jabber: anderslund@jabber.dk
GPG fingerprint: 4B50 66DE CF6E 35E3 4446 5DC1 CB23 1264 0F2C 0826

[Attachment #5 (application/pgp-signature)]

_______________________________________________
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]