Allow more granular control over syntax highlighting #35008
Nikita0x
started this conversation in
Config, Settings and Keymaps
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I want to be able to customize my syntax highlighting a lot.
For instance, it is easier for me to read types with generics, when
typed parameter
is highlighted as function parameters - I see them to be very similar.Yet in zed typed parameter is highlighted as an overall type.
I cannot highlight in zed - interfaces and types with different colors, I cannot highlight true and false with different colors, I cannot highlight different operators (for instance
...
operator) differently - because they are all operators in Zed...I checked the
highlights.scm
- some operators are swiped under the keywords category - which is incorrect.And most importantly - as I understood - the parser just does not assign any names to those tokens so I cannot even differentiate them (for instance with booleans. Why we are only limited to
@boolean
and not@boolean.false
,@boolean.true
. I am a visual, I want to see my true as green, and false as red.Unfortunately, I am not that experienced to rewrite or write additions to parser and especially scheme language, I just want to throw it out there that I and, more users - would prefer more granularity in syntax customization.
Beta Was this translation helpful? Give feedback.
All reactions