-
Notifications
You must be signed in to change notification settings - Fork 10
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
bug: different keyword color with vscode OneMonokai #88
Labels
Comments
Hi, sorry for the long wait! I'm afraid we can't make everything identical due to the differences in how the VSCode and Tree-sitter parsers handle token parsing. Adjusting settings for one language might affect another. The best approach is to use the customization settings with the require("one_monokai").setup({
themes = function(colors)
return {
-- This will change the color of enum and struct keywords in general.
["@keyword.type"] = { fg = colors.cyan }
-- Note that each language can define @keyword.type differently (in most cases).
-- If this is the case, you can specify the language name at the end.
["@keyword.type.rust"] = { fg = colors.cyan }
}
end,
}) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
as you can see, key words
enum
,struct
or even enum variant, field name have different color.Same code source in VSCode:

with NVim 0.10 and one_monokai.nvim:
Screenshots
No response
Operating System + version
macOS 14.5 (23F79)
Neovim version
NVIM v0.10.1-dev-9+g671073e71
Reproduce steps
OneMonokai
color theme.Expected Behavior
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: