Christian Clason

We need much more context, including a minimal(!) reproducing config. The `cwd` in your screenshot looks off. You should try cleaning out all the cache files and re-download the plugin.

```lua local tspath = vim.fn.stdpath('data') .. '/tstest' print(tspath) if not vim.uv.fs_stat(tspath) then vim.system { 'git', 'clone', '--filter=blob:none', '--single-branch', 'https://github.com/nvim-treesitter/nvim-treesitter', tspath, }:wait() end vim.opt.runtimepath:prepend(tspath) require('nvim-treesitter.configs').setup({ highlight = { enable = true...

Yes, if you don't use a lockfile entry, you need to specify the correct branch. This is documented in the README: > default branch in case of git repo if...

> Generating Vim 9 script is also possible, but for now I have rebuilt the colorschemes in legacy Vim script. We (Neovim) appreciate that! We include these colorschemes as part...

Then I should have commented here much sooner! (I have meant to for a while.) I can assure you that your efforts are seen and appreciated. (The bundled colorschemes used...

> Thanks! I'll take the opportunity to raise a question to everyone involved in this project and to Neovim developers if anyone is reading, since in Colortemplate v3 I have...

> No idea about the rationale, except that being compatible with less capable terminals does not seem a Neovim requirement, and “Nvim startup is not blocked on waiting for the...

To quote from the docs: > The `vim.lsp.buf_…` functions perform operations for LSP clients attached to the current buffer. So it's not about "buffer functions" but about all client functions...

Because that module is deprecated. (It's part of the old, bad, design we have replaced.)

Silly me, thinking `:h vim.lsp.diagnostic` would give me the right help tag. (Still, the remaining functions are really low-level and not on the same level as a major LSP request.)