Summary: | Color scheme will not change color of "Scripts/python" when you apply a different color on the "Built In Function" context A Builtin function like print() ,on python will stay the same syntax color. | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Humbert c <cyberhumano> |
Component: | UI: general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | minor | CC: | |
Priority: | NOR | ||
Version: | 5.3.2 | ||
Target Milestone: | 5.3.2 | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Humbert c
2019-07-25 23:56:47 UTC
Thank you for reporting this issue. This is because the configurable editor colours (part of KTextEditor, shared with KWrite and Kate) are overridden in many places in KDevelop by semantic highlighting which uses its own hardcoded colour set. You can adjust the intensity/saturation of the semantic highlighting colours by adjusting the sliders in `Configure KDevelop -> Language Support`. If these are set to 0, the semantic highlighting will have no effect and the (configurable) basic editor colours should be used. Merged with the existing report. *** This bug has been marked as a duplicate of bug 395856 *** (In reply to Francis Herne from comment #1) > Thank you for reporting this issue. > > This is because the configurable editor colours (part of KTextEditor, shared > with KWrite and Kate) are overridden in many places in KDevelop by semantic > highlighting which uses its own hardcoded colour set. > > You can adjust the intensity/saturation of the semantic highlighting colours > by adjusting the sliders in `Configure KDevelop -> Language Support`. If > these are set to 0, the semantic highlighting will have no effect and the > (configurable) basic editor colours should be used. > > Merged with the existing report. Thanks for the answer, It's a workaround that solves the "Built In Function" context color, but it "maybe" still has secondary effects on the color scheme. |