Bug 410213 - 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.
Summary: Color scheme will not change color of "Scripts/python" when you apply a diffe...
Status: RESOLVED DUPLICATE of bug 395856
Alias: None
Product: kdevelop
Classification: Applications
Component: UI: general (show other bugs)
Version: 5.3.2
Platform: Kubuntu Linux
: NOR minor
Target Milestone: 5.3.2
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-25 23:56 UTC by Humbert c
Modified: 2019-07-26 01:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Humbert c 2019-07-25 23:56:47 UTC 
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.

STEPS TO REPRODUCE
1. Settings -> Customize KDevelop
2. Editor -> Fonts & Colors -> Hightlighting text styles (Hightlight:Scripts/python) 
3.Change the "Built In Function" color

OBSERVED RESULT
No color change on your source code


EXPECTED RESULT
Should change color of your code

SOFTWARE/OS VERSIONS
Windows: 10 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

ADDITIONAL INFORMATION
same thing happens on other distros like linux mint
Comment 1 Francis Herne 2019-07-26 00:02:36 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.
Comment 2 Francis Herne 2019-07-26 00:02:51 UTC 

*** This bug has been marked as a duplicate of bug 395856 ***
Comment 3 Humbert c 2019-07-26 01:18:34 UTC 
(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.