Christian Clason

I still don't understand how this concerns VS Code: The only code paths involving https requests are 1. bumping the emscripten version (tree-sitter maintainer task, can be removed without loss);...

Ok, then the (new) `wasi-sdk` download step _is_ relevant for this. But would it be enough to gate this behind a check for an existing installation? Then you would (again)...

Let's keep vterm out of this for now. Regarding protocol, I would focus on kitty for now; that has by far the widest adoption across terminals. (And we don't want...

The point of a protocol is that it covers more than one consumer.

Yes, but Kitty is already a protocol, and supported by several terminals. That makes discouraging it in favor of a new vaporware "protocol" that is specific to _your_ GUI a...

Documentation issue. The point of `vim.lsp.enable` is to set up the `FileType` autocommand; I don't see _any_ benefit in adding code to support this from a `ftplugin`. (We _could_ consider...

No, they were _not_ doing it properly! If this is not obvious, then we need to improve the documentation. `vim.lsp.enable` is not `vim.lsp.start`.

The point is not about legitimate use cases, it's about using the right tool for the job. If you want to more control over when to start the client, use...

It's still not 100% clear to me what you are asking for here. Is it simply for `vim.lsp.enable(..., false)` to immediately stop all matching running clients? If so, that's different...

Yes, it would _really_ help if you kept to established Neovim terminology. So you want to call `enable` _manually_ to (optionally?) also start and stop any running servers. That's definitely...