Stephan Seitz

doc-extraction should go to locals, right? Adjacent to definitions since we're taking our local queries mostly from treesitter's tag queries. If you need some inspiration how tree-sitter does doc-extraction: https://github.com/tree-sitter/tree-sitter/tree/master/tags

@steelsojka yes, just use the crate I pointed you to if you have no problems compiling the rust crate and linking it with parsers you can directly use it. But...

We already started to add this doc-queries to definitions. So feel free to add the @definition.doc to the js locals.

@tom-anders you want to use this option: https://github.com/nvim-treesitter/nvim-treesitter/pull/1561

@tom-anders language injection is implemented by each editor. It is not an issue of Tree-Sitter itself. When there's a parser of doxygen it can be used by Neovim or Atom....

@IndianBoy42 is absolutely right. We could try to solve this by trying to take the context into account in our queries (not guess function declaration within function bodies) or just...

I guess this could be split into multiple PRs. If you want you can take the methods for `Session` and the set data point to the new variables widget. I...

There have also been some patches for prompt buffers which could have changed behavior. For example, REPL output is now working without the need to be in insert mode in...

We fixed that exact bug before. I wonder what's now different. This get node for the third argument is missing a check https://github.com/neovim/neovim/blob/1e5daed67693f88d3ad515cf9e2d2f6d29c48a08/runtime/lua/vim/treesitter/query.lua#L278but here it seems to get triggered for...

> The big question for me is indeed how to handle modifiers (which I think are by far the most interesting and useful parts of this feature), especially in relation...