Closed anthony-S93 closed 1 year ago
What happens if you run the :Inspect
command? Looks like it will be a semantic token being applied.
What happens if you run the
:Inspect
command? Looks like it will be a semantic token being applied.
Semantic tokens have indeed been applied, and it would appear, at the highest priority.
What do you recommend?
Yeah that is expected behaviour in Neovim 0.9. I'd suggest overwriting them in your config as part of your custom highlights
@olimorris Fixed it.
Thanks for the assistance and for the quick response as well! Cheers.
Update:
Incidentally, for those of you who prefer Treesitter highlighting over semantic highlighting, here's how you can turn semantic highlighting off. In the on_attach(client, bufnr)
passed to the language server, add this line:
client.server_capabilities.semanticTokensProvider = nil
Great to hear it. As of yesterday, you can set highlight groups to be {}
. Which allows you to unset any
Great to hear it. As of yesterday, you can set highlight groups to be
{}
. Which allows you to unset any
@olimorris Even those that are linked to other groups? Because I can't seem to disable @lsp.type.variable.javascript
with ["@lsp.type.variable.javascript"] = {},
Yep. Assuming they've been set with the default argument.
Can you share the example Javascript code you're working with?
Just something as simple as:
As you can see, @lsp.typemod.variable.defaultLibrary.javascript
has already been disabled.
Hang on. It's working now. I deleted the packer_compiled.lua
file and then regenerated it.
Great to hear. Was just going to say this is what I'm seeing:
Great to hear. Was just going to say this is what I'm seeing:
For some reason my packer_compiled.lua
didn't get updated even after a :PackerSync
. This isn't the first time this has happened now.
I'd had similar weird issues in the past so made the switch to Lazy a while back and haven't looked back.
I'd had similar weird issues in the past so made the switch to Lazy a while back and haven't looked back.
@olimorris
So I followed in your footsteps and switched to lazy.nvim
as well. lazy.nvim
, aside from providing a nice UI for plugin management, cut down my nvim
startup time from 140ms
to 38ms
(which is a bit insane if you ask me). So, yeah. Thanks for yet another helpful suggestion. You were the one who introduced me to nvim-ufo
last time as well.
Just out of sheer curiosity, what does your startup times look like?
140ms
to 38ms
? That is insane! Mine is actually at around 140ms
right now so I may have to dive into that. I have maybe 80 plugins. How does that compare to yours?
I have found Lazy to be awesome; even restructuring the whole of my config. Just feels so much leaner and organised.
have maybe 80 plugins
140ms
with 80 plugins is an insanely good number.
I have 30 plugins and with lazy.nvim
, my start up time averages at about 40ms
if I just launch neovim without launching a file. If I open a file, the average is around 50ms
.
I guess packer
is just slower, since it took neovim more than 100ms
to start up with the same number of plugins.
Your OneDarkPro config
Error messages
No response
Describe the bug
What I expect to happen
In onedarkpro's config, I set the
@variable.builtin.javascript
highlight to sea green. The use oftsserver
shouldn't mess with my highlighting.What actually happened
The color was loaded as sea green, but then got overridden by the default (yellow) after the language server loads. I can confirm that the language server is the culprit. The problem disappeared after I removed the configuration for
tsserver
- as in I deleted these lines:To be fair, I wasn't sure if the issue lies with
nvim-lspconfig
,typescript-language-server
, oronedarkpro.nvim
. But I figured I would report it here first.Reproduce the bug
Steps to reproduce: 1) Create a test directory. 2) Create the minimal config file I mentioned above in the test directory. 3) Create a test file
testing.js
4) Add the following line to the test file:5) Open the file with neovim using the minimal config file mentioned above.
Final checks
minimal.lua
config file above and still get the issue:checkhealth treesitter