Christian Clason

Note: these luacats files seem umaintained. We should try to get them [upstreamed](https://github.com/luvit/luv/issues/632) (so we can point to them in our `.deps` checkout) or, if necessary, bundle them as `meta`...

Yes, that's how I could tell :)

Needs docs and a news entry. It would help if the proposed API (for several representative use cases) was added to the PR description.

We should also add a health check for this (like we do for `rg`); see https://github.com/nvim-treesitter/nvim-treesitter/blob/e0d029bfdc1ea0da00356203b5afbe70ca9c74c1/lua/nvim-treesitter/health.lua#L87-L93 Here it's important to show the _full_ version output, including all build flags (since...

You need to add the new module to https://github.com/neovim/neovim/blob/59c45b22d9616cda448b3c3dddd3e9274c830ca3/src/gen/gen_vimdoc.lua#L135

As a plugin author, I don't need it. Let's keep this to MVP.

No, at least not in this PR. You can (and should) use environment variables for local configuration. **Reminder:** This is meant to be a simple function mainly for the (internal!)...

> I suggest starting with a vim.net.fetch() which, at first, might only do the basic "download" case, while keep the door open to expand it later. But isn't that exactly...

> Either this PR or https://github.com/neovim/neovim/pull/34140 should be closed. We don't need two separate interfaces until proven otherwise. Yes we do -- one high-level function for downloading stuff and one...

I don't think that's a good idea (that's _exactly_ what killed the last attempt!) but will hold my peace from here on out. It's all yours.