-
Notifications
You must be signed in to change notification settings - Fork 33
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
syntax highlighting for tsx/jsx not working #39
Comments
This is the case for me as well. It looks like it going to load the correct colors but the white color turns dark after "tsserver" lsp finishes loading. I don't know if that helps or not. |
I'm having this same issue... Anybody find a solution? |
Same, once treesitter kicks in, it looks like garbage. The only reason I don't use this theme anymore. |
This has worked for me: local default_setup = function(server)
require('lspconfig')[server].setup({
on_init = function(client)
client.server_capabilities.semanticTokensProvider = nil
end,
})
end
require('mason').setup()
require('mason-lspconfig').setup({
default_setup,
...
}) |
I've been able to get closer to the desired result by adding this to ['@variable.builtin.typescript'] = { fg = p.blue2 },
['@lsp.type.variable.typescript'] = { fg = p.text },
['@lsp.type.parameter.typescript'] = { fg = p.text },
['@lsp.type.property.lua'] = { fg = p.text },
['@comment.typescript'] = { fg = p.blueGray3 },
['@comment.documentation.typescript'] = { fg = p.blueGray3 }, It seems like there's a priority issue with Treesitter and lsp semantic tokens, where lsp semantic token take over treesitter in priority. I'll try to open up a PR soon once I get to something I like EditPR open as a work in progress: #43 |
I saw this issue was resolved by #32.
But it's not in my lunar vim.
The text was updated successfully, but these errors were encountered: