tokyonight.nvim looks very purple

[TymekDev]

At this point, I am not sure whether it has always looked like it and I haven't noticed or if something has changed recently. To me Astro and Lua files look especially monochromatic to me with purple being used all over the place. Here is a comparison with nightfox (nordfox flavor):

I am using Neovim v0.9.0 with all parsers and plugins up to date.

Has it always looked like that?

[folke]

You're using the moon style of tokyonight and you don't have treesitter enabled.

[TymekDev]

Asciicast I have linked showcases working :TreesitterPlayground and :TSHighlightCapturesUnderCursor, though. I will try to troubleshoot it and see if the issue persists with a minimal reproducible example

[folke]

I already told you it's not a Tokyonight issue, so I don't need a minimal repro. I won't further look into this. You can't expect me to debug everyone's configs. I'm sure you'll figure it out.

[TymekDev]

It is a matter of having LSP enabled. After learning about :Inscpect from #347, I gave it a go:

I looked up :h lsp-semantic-highlight linked in the issue and it has a following snippet:

-- Hide all semantic highlights
for _, group in ipairs(vim.fn.getcompletion("@lsp", "highlight")) do
  vim.api.nvim_set_hl(0, group, {})
end

Adding it to my config function for tokyonight resolved this issue. There is also hint about wrapping the above in an autocommand on ColorScheme.

Do you consider it a valid issue to add a note about it to README or perhaps adding the above code to run on colorscheme tokyonight?

[folke]

Semantic tokens are fully supported for TokyoNight and make the colorscheme even better. So again, something is wrong in your config. You don't need to set those hl groups manually

[TymekDev]

It completely went over my head that at some point I have switched to a fork of tokyonight.nvim that got stale in the meantime... I am sorry for the confusion.

[folke]

This is how storm is supposed to look like:

Moon:

[TymekDev]

Solution to this would be not being a dum dum and updating your fork as a first troubleshooting step. 🤦