bug: different keyword color with vscode OneMonokai

[xanahopper]

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

1. open same code in VSCode and nvim with OneMonokai color theme.

Expected Behavior

No response

Additional context

No response

[cpea2506]

Hi, have you tried to disable semantic token highlighting? If semantic token highlighting is enable, some of colors will be decided by language server instead.

If you have disabled it but the issue still happens, please take a picture and note on what are the most clearly difference you see. I will take my time for a look. Or if you know what to do, please consider a PR, that would be so helpful.

Note:

The color scheme for Neovim is designed in a way that cannot totally mimic the original one from VSCode because of the way they treat the language tokens.

Tips:

You can use :Inspect from within Neovim to see the token's highlight group under your cursor. The result will be like this:

See more:

• Sematic Highlighting

[xanahopper]

I'm not sure how to disable semantic token highlighting, but I tried

• disable Rust LSP
• disable nvim-treesitter's additional_vim_regex_highlighting
• disable whole nvim-treesitter

the first two operations did not make a change. After disable LSP & treesitter, color changes, like VSCode but not exactly same.
It becomes like this

seems like with nvim builtin syntax, it lost lots of info for colorscheme.

I dont know what to do next.

[xanahopper]

I reverted all disables and re-enable LSP and Treesitter, do some inspect.

struct, enum

Unnamed enum variant

[cpea2506]

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 Inspect command to adjust the colors to your preferences. For ex:

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,
})