We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Now nvim nightly support semantic token neovim/neovim#21100
References: sainnhe/gruvbox-material#162
The text was updated successfully, but these errors were encountered:
Is this different from #101?
Sorry, something went wrong.
Yeah OFC. There are some differences. Now if i use semantic token. My eyes are captured by the purple
This experience is really bad
feat: update tokens
cc347e2
ref #107
Merge canary (#114)
4eac261
* feat!: use new highlight api * feat: support custom highlight blending Example: ``` { highlight_groups = { StatusLine = { bg = 'love', blend = 10 } } } ``` * refactor: move config into separate file * wip: update semantic tokens * ci: add issue templates Thanks to https://github.com/folke/lazy.nvim for the inspiration! * ci: fix template formatting * chore: update editorconfig * fix: decouple more backgrounds from floats * change `@tag.attribute` to iris * add cursor highlights Closes #121 * match link underline colour * improve `dim_nc_background` behaviour ref #123 * feat: expose each variant as individual theme ref #98 * feat: update tokens ref #107 * feat: distinguish between `CmpItemKind`'s
mvllow
Successfully merging a pull request may close this issue.
Now nvim nightly support semantic token neovim/neovim#21100
References: sainnhe/gruvbox-material#162
The text was updated successfully, but these errors were encountered: