Christian Clason

Not a blocker, just nice to have. We can push to 0.9 if there are more urgent things.

That wouldn't change anything -- somebody needs to make a PR with a fix (which even the resident experts struggle with).

> Also, I have yet to see a statement from the Neovim core-team that clearly states that plugin authors should stop using CursorHold. Until that happens, plugins, both old and...

There is no "CursorHold position" -- there are issues with that autocommand in connection with timers; the problem is known but a fix is not; on the other hand, there's...

Is this something we want to revisit? Or is it superseded by nvim-treesitter's module system (i.e., this is the approach that should eventually come into core, when stable)?

We should revisit this as part of the "Lua highlighting in core" goal for 0.8. (scope should be buffer-local, though?)

An alternative would be to mirror the `vim.lsp.start({...})` pattern, where the table could contain options like whether regex syntax is still run, the location of the parser and the queries,...

While I agree that a) the first point is the most critical and b) they can be addressed incrementally (so I'd welcome focused PRs that address parts of it), I'd...

(can reproduce on macOS)

I can no longer reproduce this on master (proper `E5500` error, no crash).