Damjan 9000

Yes, bring it up to Treesitter, nothing kickstart can do about it.

@feoh your suggestion works. But I think it's not clean that a plugin has the spec split into two files. Please open a PR with your solution so there are...

I wonder whether you have the old kickstart which used onedark theme by default, or do you use the latest kickstart which uses tokyonight by default but then switched it...

You can try disabling treesitter highlight, something like this: ``` diff --git a/init.lua b/init.lua index 013fcc2..9af7463 100644 --- a/init.lua +++ b/init.lua @@ -796,6 +796,7 @@ require('lazy').setup({ auto_install = true, highlight...

I tested this and the text appears just fine with the default kickstart, perhaps your issue lies in your own customization, perhaps it's caused by the `colorscheme` that you changed,...

@vimkim my neovim is 0.10, but I also have not noticed such an issue previously with 0.9.5. From your screenshots it appears to be an issue with your terminal colors....

@proofer when using gcc on windows it will still produce .so libraries. @dogusmiuw This issue appears to be possibly the same as: https://github.com/nvim-lua/kickstart.nvim/issues/904 which was solved by upgrading the gcc...

Well, I would also like to know why is this necessary, what are the benefits of swapping telescope with snacks picker? One downside is that existing kickstart users who are...

I'm not seeing this. Also pressing `K` on `vim.opt` shows proper definition:  Can you make sure you have the latest kickstart and update all the plugins to latest versions...

@aski I just tried it and you are right, if the files are outside nvim config location the hover doc is not complete but I don't get any diagnostic warnings...