Stephan Seitz

Some numbers for https://github.com/tormodatt/tree-sitter-kotlin (kotlin file in repo, query file: https://raw.githubusercontent.com/nvim-treesitter/nvim-treesitter/master/queries/kotlin/highlights.scm ``` ❯ tree-sitter --version tree-sitter 0.19.4 (6dd41e2e45f8b4a00fda21f28bc0ebc6b172ffed) tree-sitter-kotlin on  master [!] is 📦 v0.0.1 via ⬢ v15.12.0 via...

Hi! It looks like this bug is triggered by the `#lua-match?` in our queries. `#lua-match?` is implemented here: https://github.com/theHamsta/neovim/blob/a41dcb305e7b1349a6eaceb6844e7abbf011ecde/runtime/lua/vim/treesitter/query.lua#L315-L315 Can you report this issue at http://github.com/neovim/neovim? It seems like `vim.treesitter.get_node_text`...

Do you want to create a PR? All you need to do is add a `branch = "next"` to the install information of the parser (leave the original URL!). To...

I think it is ok to try a buffer for full path first. Thank you for your contribution!

Thank you for reporting! I tried to add it in #93

In my opinion, there should be a better way to tie the queries to a specific parser. There's a similar problem when a parser implementation in nvim-treesitter is switched or...

@MunifTanjim maybe the one could just load the base queries from the directory on which the parser is installed. Philosophy: you bring the parser, you're responsible for the queries or...

> maybe the one could just load the base queries from the directory on which the parser is installed. Philosophy: you bring the parser, you're responsible for the queries With...

> I would like the equivalent of :LspInfo that dumps only what is relevant to debug my current buffer, maybe something like :TSInfo ? So you would like to have...

> I've tried :h :TSInstall to no avail, so I wonder what's the difference between TSInstallFromGrammar and TSInstall ? Might be worth adding to documentation. I just tried to fix...