Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 520512 - Syntax coloring preferences are not honored by Dark theme
Summary: Syntax coloring preferences are not honored by Dark theme
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-03 07:34 EDT by Utku Ufuk CLA
Modified: 2021-03-24 04:03 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Utku Ufuk CLA 2017-08-03 07:34:10 EDT 
After I installed Genuitec's Darkest Dark theme, i tweaked some syntax coloring options. Most of them are persisted after shutdown, but syntax coloring options for Abstract Classes, Enums and Annotations are not completely persisted. (Color settings for these types are persisted but style settings are not.)

For example Abstract classes reset to bold, Annotations reset to bold & italic, and Enums reset to italic after restarting Eclipse.

I am facing this issue both on Windows 10 and Ubuntu 16.04 LTS.
Comment 1 Dani Megert CLA 2019-02-22 09:43:42 EST 
*** Bug 544714 has been marked as a duplicate of this bug. ***
Comment 2 Eclipse Genie CLA 2021-03-24 04:03:57 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.