Bug 23908

Summary: KDevelop doesn't notice file updates by other applications
Product: [Applications] kdevelop Reporter: djarvie
Component: kdevelop 2.x (obsolete)Assignee: KDevelop-Devel List <kdevelop-devel>
Status: CLOSED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description djarvie 2001-04-08 18:11:22 UTC 
(*** This bug was imported into bugs.kde.org ***)

Package:           kdevelop
Version:           KDE 2.1.1 
Severity:          normal
Installed from:    SuSE RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: SuSE 7.0 i386 RPMs

KDevelop 1.4.1 often fails to detect when a file which it has open for editing is updated by another application. As a result it would be very easy to accidentally overwrite changes made by the other application.

Sometimes switching to another file in KDevelop and then back to the first (changed) one will trigger KDevelop to notice the update. But other times it is not easy to make it notice. It is even possible to have an outdated version displayed while it compiles the changed file and when you click on a compile error it takes you to the line in the unaltered version of the file instead of the version which the compiler actually compiled!

(Submitted via bugs.kde.org)
Comment 1 Per Ångström 2001-08-19 18:37:00 UTC 
This is still a problem in version 2.0 final. This behaviour 
is embarrassing and must be fixed. It has caused me trouble 
and I'm surely not the only one.

Look at Emacs or Developer Studio for inspiration. It should 
simply not be possible to make a single edit without 
refreshing the editor after an external change to the current 
file.
Comment 2 Per Ångström 2003-10-15 19:53:19 UTC 
KDevelop 2.1.5 is still slow in detecting files that have changed on disk. I also find that "Reject" in the confirmation dialog doesn't reload the changed file  from disk.

How to reproduce:
1) Open a file in KDevelop.
2) Open the same file in Kate.
3) Make some changes to the file in Kate, and save your changes.
4) Switch to KDevelop.

(Here I expect a warning dialog)

5) Make some changes to the same file.
6) Try to save the changes.
7) In the confirmation dialog, choose "Reject".

Actual result: the changes made in KDevelop are still there. The changes made in Kate are not reflected.

Expected result: the file should be read from disk, showing the changes made in Kate.

----

If you reverse the roles between KDevelop and Kate, you will notice that Kate behaves much more reliably.
Comment 3 Amilcar do Carmo Lucas 2003-10-15 22:19:17 UTC 
Sorry, KDevelop 2.x is no longer under development.


Like it says in the bug status this bug has been fixed in KDevelop 3
You are strongly advised to update to the latest CVS version of KDevelop3, code name gideon, take a look at:
http://www.kdevelop.org/index.html?filename=branches_compiling.html
for all the details you need. If you find a problem or need help please send a mail to the mailing list:
http://www.kdevelop.org/index.html?filename=mailinglist.html
or drop us a line at the channel #kdevelop on the server irc.kde.org using ksirc, for example.
Please use the CVS version and compile it yourself because that way you can easily patch it if a bug is found.

KDevelop3 can open Develop2 projects. To do so, goto the "Project -> Open Project ... " and select
"KDevelop 2 Project Files" in the "Filter:".
Comment 4 Per Ångström 2004-02-07 12:07:49 UTC 
OK, so I installed KDE 3.2 (on SuSE 9.0) and KDevelop 3.0.0 with it.

Performing the same test will now give an even worse result: it seems that KDevelop 3.0.0 completely ignores any external changes that have occured.

Bug #58572 seems to confirm this observation.