Christian Clason

I forgot to add this yesterday: Telescope _already_ has the concept of extensions, and those are pretty well-used already. While I strongly believe Telescope core should come with a set...

TL;DR: Leverage Github tooling (CODEOWNERS, Teams, a custom bot) to allow team members to stop subscribing to _every_ issue/PR/commit to Telescope without missing the stuff they are actually interested in....

I'm also having this problem since the latest snapshot, *but only on one (out of three) machines* (with identical `init.vim`). I haven't been able to find out what difference there...

I also have `background=dark` (with my own colorscheme). But as I wrote, it only happens on one machine; other machines with the exact same config are fine, as is terminal...

Looking at `scriptnames`, it looks like the non-working instance doesn't read my `init.vim` for some reason -- `packages` (and `ginit.vim`) are sourced correctly, though. The only other difference is that...

vimR does not use the msgpack API to link to an external binary but bundles its own `libnvim`. So upgrading the neovim version requires a full rebuild of vimR. Recent...

Duplicate of #846 (VimR does not use your system neovim but links against its own "libnvim". There's nothing you can do until @qvacua releases a new snapshot built with a...

First step is to bisect which exact tree-sitter (not Neovim!) commit broke the org parser. You should also report it on the parser repo since it's possible that the parser's...

The effects seem to be known, then: https://github.com/tree-sitter/tree-sitter/pull/1783 Seems like external scanners indeed need to account for the new behavior and can no longer rely on empty tokens being ignored....

That is a separate question (timeouts) that has been discussed before. But _this_ issue needs to be fixed; it's just how things work. A timeout would still lead to broken...