You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, this repository is missing a maintainer. But I am currently maintaining a fork.
The "dull" colors can be attributed to the outdated and modified color palette that was used here. This has been resolved in my fork (it now uses the official colors from the ayu-colors repository).
For the "different" colors, this is more difficult. Since the syntax highlighting is completely different from one editor to another, it might not be possible to share the exact same highlighting. But since I still agree with the differences, here is my proposition:
These are 3 instances of Neovim:
The first one has the current highlighting from my fork.
The second has some changes to make const, let and var use the "Keyword" highlight instead of the "Type" highlight. I also changed the arrow function to use the "Operator" highlight.
The third is using the built-in TreeSitter highlighting in conjunction with the TreeSitter plugin. It is what I personally use and I treat it as my "source of truth".
Hi, the colors in ayu dark for neovim are dull and different from the colors shown in the screenshots, or those in the themes for other applications.
As an example, here is a screenshot comparing ayu-vim (on neovim) with ayu-vscode:
The text was updated successfully, but these errors were encountered: