Version: (using KDE KDE 3.5.8) Installed from: SuSE RPMs Currently you can change all colors one by one. But it would be useful to: * change all Kate-specific colors * decide to use or not system colors (i.e. to use common part Kate<->KDE from KDE) * if not -- ability to change them (for Kate only of course)
Kate has far to many different things for which you can set colors to make proper use of the system palette. And it doesn't make sense to extend the system palette just for 1 application, IMHO.
> And it doesn't make sense to extend the system palette just for 1 > application, IMHO I am not sure we understand each other. I am not talking about extending system palette -- I talking about "dividing" Kate palette into common-part (system) and Kate specific. > Kate has far to many different things for which you can set colors to make > proper use of the system palette. Exactly! But some of them are from system. Example -- background color. If you want to customize it, fine, but if not -- it could be just window background. So this color could be read from system. On the other hand keyword color is Kate specific, so it is always possible to customize it. Maybe I add some perspective: 1) you choose KDE colors 2) you choose Kate colors 3) you change KDE colors, background for example 4) you have to change in Kate too (4) is bad. Changing colors in KDE should have impact on KDE apps -- today it has very random (partially changed color) so you have to manually set background colors in all KDE apps. Not nice.
Compare it KMail and then see this report: http://bugs.kde.org/show_bug.cgi?id=115959
Ah, indeed I misunderstood. And actually thats a bug in Kate, not a wishlist item. Changing the severity. Kate needs to respect the KDE wide palette and AFAIK KDE4's Kate is supposed to use the system palette as far as it can/makes sense.
Changing the some colors with the system palette and not the kate schema may potentially lead to unreadable files in kate, which is why it works like it does.
I guess you're referring to cases where a highlighting or some such doesn't play well together with the system palette? Well, thats quite expected isn't it? If a user changes the system palette to something different its his responsibility to also change special color schemes in apps like kate or kmail to work with that new color scheme. As it stands now kate is completely ignoring whatever color scheme the user sets and thats not good.
Confirming this. In KDE4, the palette has enough foreground roles that the default katepart colors (for highlighting, anyway, some markers, folding etc. are still hard-coded) all come from the system palette. Individual highlighters with hard-coded colors should be fixed, but these can be handled individually. Some way for katepart to forget customizations and go back to the system colors (or at least to not "remember" the system colors when the user has not changed them) was already on my TODO list, so this is definitely something that should be fixed.
This bug still exists; it's extremely jarring when you switch to a dark color scheme and discover that, not only does the editor ignore the change(shocking the eyes for no good reason), but that you need to fix the entire color scheme manually.
*** This bug has been marked as a duplicate of bug 219027 ***