Version: 3.2.1 (using KDE KDE 3.2.90) Installed from: SuSE RPMs Compiler: gcc 3.3.3 OS: Linux This might be a duplicate of bug 75917, but since two problems are reported in that one, I'll open a new. When a file has been edited under Windows, all lines are different because of CR/LF. However sometimes Kompare reports that the file is identical to the original, unedited file. For example: diff externalprocessview.hnew ../rtk/src/externalprocessview.h indicates that all lines are different, however kompare externalprocessview.hnew ../rtk/src/externalprocessview.h indicates that the files are identical, where the .hnew file is the windows edited file.
I forgot to mention that even if the edited file contains "real" changes apart from the CR/LF's, kompare still indicates that the files are identical.
I believe this has to do with the fact that kompare uses the -bB diff flag by default. Try unsetting this one in the diff options. If that works close the bug please.
I can confirm this bug, but it is even worse: Try to compare two _completely_ different files, like a README with your favorite .c-source file (not even a single line is matching): The result is that kompare will not only report no differences, but also display one of the two files in both windows! So the above reported error is just a very special case of this (all lines are different), but since most editors won't show you the different CR/LF (including the displays in kompare), this was unnoticed before.
In the reported case both the options "ignore added or removed empty lines" and "ignore changes in the amount of white space" were turned off in Kompare. However when I turn these options on and restart kompare (apply doesn't seem to have any effect...) it shows some (!) changes at the beginning of the file but still ignores some real changes (not CR/LF) related. For ignored changes it shows the contents of the first file in both the left and the right view. Strange behaviour.
For files with dos/Windows line ends, Kompare doesn't show changed or deleted lines, only inserted lines, and displays the second file as if it was just the first with those insertions. If the two files are completely different, every line is effectively a changed line, and the two files are shown as identical to the first. The commandline programs unix2dos and dos2unix can be used both to confirm this bug and as a temporary work-around for those comfortable on the command line.
This is all related to the -bB option, closing as a duplicate of 75917 *** This bug has been marked as a duplicate of 75917 ***
I've just proved the KDE 3.3.2 version: The problem is solved! Thank you very much!