Christian Clason

For the sake of completeness, this would require turning Hints into errors in `make luals`. Also of note is that we'd need to include `luals` in `make lint` then, which...

Indeed, but I think it's easier to continue here rather than move the concrete information here over.

If somebody wants to go down the linked list of luachecks, verify them against the latest(!) luals, and add any missing ones, that would be appreciated. (`0xx` and `6xx` are...

(Note that the main thrust of Famiu's work is native table options, which require a lot of effort to get right. Lua(!) function handles are a much smaller scope --...

Also, the added interface here will be the same no matter how it's implemented (now or later), so I don't see any danger of conflict. (Could be wrong, of course.)...

> > On the other hand, I'd like to see *expr options included here (for vim.treesitter.foldexpr, if nothing else). > > Done. Just remembered #18997 (`keywordprg`, which is not like...

not high priority in any case; just wanted to mention it because it seemed related.

Bumping this now we're on the 0.12 dev cycle. Could you start with rebasing? (Most of the diff is from moving tests around.)

PUC Lua test failures look germane.

Duplicate/part of https://github.com/neovim/neovim/issues/22478 See also https://github.com/neovim/neovim/issues/27811