-
-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overridden palette elements must be "re-exported" in specs #303
Comments
By the way, I noticed lua operators are highlighted as keywords rather than operators, and I think it's due to this line
If that was intended to be syn.operator, I could send a PR. |
This was done on purpose because GitHub's syntax highlighting for Lua deviates from the norm and has "keyword-colored" operators (i.e. usually a reddish or coral color). In other words, currently GitHub uses their "keyword" color for operators when it comes to Lua. |
Indeed! Then perhaps they have a bug? ;-) Anyway, I solved it with this local workaround: ['@operator.lua'] = { fg = 'syntax.operator' }, |
Yeah, although it may be a style/design choice. |
@codewiz These are the items/keys of the |
I override a few colors in the base palette of my theme:
I expected these values to be directly usable like the originals:
However, none of my overrides works until I "re-export' them at the specs level:
I assumed it's a bug, but I might be misunderstanding the underlying design.
None of the examples in the README covers exactly this case.
My full config is here: https://codewiz.org/pub/dotfiles/init.lua
The text was updated successfully, but these errors were encountered: