https://bugs.kde.org/show_bug.cgi?id=395856
--- Comment #25 from Petr <kobalicek.p...@gmail.com> --- Hey we ALL have open source project, right? Who is the most proficient person to fix an issue in a project that he knows? You know, I compile my own KDevelop and I really tried to fix it, but if you read the discussion there is some interesting comments: """ I understand your complaint. You are also not the first person who is unhappy with this. I'm just saying fixing it is (both technically and logically) not as simple as just adding five entries to a config list, except if you are okay with having two separate dialogs for configuring colors (which I wouldn't like to have) ... """ So, to tell you something - I have no idea how to fix this even if I allocate time for it. So instead I spend my time on my own projects, because there I have an idea about what to do. I think that this issue is a failure of both KDE and KDevelop teams to cooperate - because KDE team doesn't want properties in color settings that are not used by KTextEditor component and KDevelop team doesn't want its own color settings that would drive the semantic highlighter! Now, tell me how I can fix that? Can you propose how this could be fixed in both KDE and KDevelop so both projects and also users are happy? Because I have no idea and spending time on something that has no chance of being merged doesn't motivate me to do so. -- You are receiving this mail because: You are watching all bug changes.
