Version: (using KDE KDE 3.2.3) Installed from: Mandrake RPMs OS: Linux The problem is that if there are some ^M in the diff file or in the source files, then the display is completely wrong. I've attached a diff file so you can check what's wrong (note: tkdiff is also affected while vim -d or xemacs are not as they display "^M" instead of a new line). See example in attachment.
Created attachment 9189 [details] diff file containing some ^M that disturbs kompare - This diff file contains some ^M that disturbs kompare and tkdiff. - xemacs and vim -d are able to handle the result correctly. (so you can see what's going wrong).
There's a bit of history here: Oliver emailed me privately about this, and I requested that it be filed here. I've tested the file and confirmed the bug. The problem is not files using ^M as a newline, but files intentionally using ^M, e.g in a regexp - examine the file attached by Oliver in vim for a better understanding. Oliver: Thanks very much for going through the bug-reporting process (: I'm leaving this assigned to bruggie for now since he's more familiar with the parsing code than I am myself, but I may take a look at it anyway. Cheers, Jeff
This is a nasty little sucker. If I have some spare time this weekend (which I expect not to have) I'll look into it but I can't give you any promises.
*** Bug 104458 has been marked as a duplicate of this bug. ***
This is gonna be a little spammy... I'm reassigning everything that's currently assigned to bruggie (who's been the default assignee for bugs since time began) to the new list address. Bruggie: if you're working on one or more of these atm, please snatch 'em back.. Everyone, esp. Joshua and Bruggie: if this genrates 33 mails, my sincere apologies..
is there some informations about this bugreport ?