From kde-bugs-dist  Sat Mar 13 07:26:56 2004
From: Christian Mueller <cmueller () gmx ! de>
Date: Sat, 13 Mar 2004 07:26:56 +0000
To: kde-bugs-dist
Subject: [Bug 77185] Open a file in read-only mode if it has already been
Message-Id: <20040313072656.943.qmail () ktown ! kde ! org>
X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=107916282414825

------- 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=77185      




------- Additional Comments From cmueller gmx de  2004-03-13 08:26 -------
> A smarter approach tahn the proposed, and that 
> could make everyone happy could be the one adopted 
> by KATE - warn a user whenever a file has changed 
> on disk - menaing that the other party using 
> it had commited his changes - and offer to reload. 

Yes, that's a common approach, not only in KDE.  
Emacs does it this way, and Eclipse even warns you as soon as 
it detects a change, even before you try to save. 

But: 
- Does it work over IOSlaves? 
- Does it work with automatic down/uploading (for apps that don't 
  support IOSlaves directly, like OO.o)? 
- What will you do if the app detects the file has changed
  (after you have spent an hour editing it)? 
  How will you merge a koffice document?  
- It would be better than nothing, but being notified that 
  you may have issues with concurrent changes *before* you make  
  yours is a far superior solution, IMHO.

So, no, this not an approach to make everyone happy.