Bug 56203 - It would be nice to show the real changes within a line with diferent colours
Summary: It would be nice to show the real changes within a line with diferent colours
Status: CLOSED FIXED
Alias: None
Product: kompare
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Otto Bruggeman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-21 12:07 UTC by Amilcar do Carmo Lucas
Modified: 2009-11-22 12:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Ports the latest CVS version to KDE 3.1.x and activates the in line diffs (7.56 KB, patch)
2003-11-13 20:38 UTC, Amilcar do Carmo Lucas
Details
same idea implemented in trac (87.22 KB, image/png)
2006-06-02 13:02 UTC, Mathieu Jobin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Amilcar do Carmo Lucas 2003-03-21 12:07:03 UTC
Version:            (using KDE KDE 3.1)
Installed from:    SuSE RPMs
OS:          Linux

Sometimes the only diference is one character in one line.
Kompare higlights the entire line which is ok but it would
be even nicer if it highligted the changed character(s) with
another color.

Thanks
Comment 1 Otto Bruggeman 2003-03-22 19:51:34 UTC
Yes this is something i want to implement eventually, might be ready for 3.2 
but dont hold it against me if i can't finish it before that.
Comment 2 Otto Bruggeman 2003-09-09 22:36:02 UTC
Due to a screw up on my side (i forgot to add this to the 3.2 featureplan) i doubt it will be in 3.2. I dont want to bother the release dude (Stephan Kulow) with a request for inclusion. Dont want to create a precedent. I think i'll release a seperate version of kompare around 3.2 (maybe some beta's before that with this in-line difference feature enabled).
the current version is very slow with large differences and with multiple files even on a dual amd mp 2400+ so i'll have to tweak it a lot.
Comment 3 Otto Bruggeman 2003-11-13 16:52:07 UTC
Fixed in CVS, but i wont activate it until after 3.2 is branched and then in what will be KDE 3.3 (or will it be 4.0?) only. There will be no backport but if you are smart you can activate it quite simply in the 3.2 version since it is in CVS before the branching has begun :) But dont bitch if there are problems with it, officially it does not exist in 3.2 ! :)
Comment 4 Amilcar do Carmo Lucas 2003-11-13 17:41:03 UTC
Please consider activating it.....please.
We now have a longer beta period where you could test it.
It's a killer feature for the entire KDESDK package!!

Thanks for implementing it.
Comment 5 Amilcar do Carmo Lucas 2003-11-13 20:38:16 UTC
Created attachment 3203 [details]
Ports the latest CVS version to KDE 3.1.x and activates the in line diffs

Again, many thanks for coding it.
Comment 6 Otto Bruggeman 2003-11-20 02:12:39 UTC
You're welcome but there is a small flaw in your patch. You delete the *this << "LANG=C" by commenting it out but it was needed for some stuff but i cant remember what it was anymore. You should use the 3.1 way of using setEnvironment( "LANG", "C" ); Then it should work properly.

And you already know the reason for not activating it in head or even backporting it to the branch. This is supposed to get stable and that wont work if people keep adding new features. The time has come to fix stuff and make this release even better then all others by having as few open bugs as possible. I'll address the other bug you reported about saving asap. Thanks again for reporting the other bugs and creating this patch :)
Comment 7 Mathieu Jobin 2006-06-02 13:01:23 UTC
euh, I'm running KDE 3.5.2 and this does not seems to be part of kompare yet.
why is this bug CLOSED as FIXED ?

Comment 8 Mathieu Jobin 2006-06-02 13:02:48 UTC
Created attachment 16428 [details]
same idea implemented in trac

just to give a visual example I took a screenshot of trac which does exactly
what is requested in this bug. please implement this.

thanks
Comment 9 esigra 2009-11-22 12:06:24 UTC
This bug seems to have reappeared in KDE4! It worked in KDE 3.5.10 but no longer in Kompare 4.0.0 in KDE 4.3.3 (or 4.3.1).