Dear Joachim, kdiff3 is by far the best overall diff utility I've found, and free, thanks so much.
Similar to wefing (bug 1710665) the one limitation that makes me sometimes need other tools is in selectively ignoring comments.
I use the tool to compare log files from my own test applications where some information is known to be different between logs.
I currently identify this with // end of line comments but neither the built-in comment processing or the preprocessors seem to handle those very well, and it is certainly not easy to set up even if possible.
There are two aspects: 1) defining the text to be ignored and 2) specifying how to display or not the ignored differences.
1) Whilst using a regular expression would be useful, I am currenetly quite happy with a simpler comment character definition. Inline as opposed to end-of-line comments would also be useful but less essential for me. Just a well supported end-of-line comment would do well for me.
2) In terms of display, it's important to be able to completely not display ignored differences, so that real differences are not swamped. That applies both to the colour coding in the directory listing and in the text display panes. This is the part that seems to have no explicit control today, and by default even ignored differences are treated like whitespace differences and unconditionally shown in the directory summary and difference panes.
best regards Julian
+1
Being able to ignore lines that match a pattern would be very powerful; because some changes may be expected while some may not. For example in my current case I have 3500+ differences between two files, and either 99% or 100% of them are expected differences. Guess who has to find out :(