install treesitter grammars

[bugsbugsbux]

I've searched open issues for similar requests

• Yes

Is your feature request related to a problem? Please describe.

nvim-treesitter was archived. all i wanted from it was a simple way to install treesitter grammars so highlighting works well. from a user's perspective this
is exactly what mason does for all other external things (lsps, daps, formatters, ...)

Describe the solution you'd like

take the info from https://github.com/nvim-treesitter/nvim-treesitter/blob/main/lua/nvim-treesitter/parsers.lua and have a new category "treesitter grammars" allowing to install these with mason

Describe potential alternatives you've considered

continuing to use unsupported nvim-treesitter

Additional context

No response

[TheLeoP]

all i wanted from it was a simple way to install treesitter grammars

nvim-treesitter also used to maintain the queries required to make each grammar useful to Neovim. Queries that are tied to a specific treesitter grammar commit and a specific editor. So, it's not that simple

[bugsbugsbux]

well, if you need queries so tightly coupled with an editor specific grammar, that everything breaks if it gets a bit out of sync, i guess this treesitter stuff is pretty useless and ill rip it out completely before i depend too much on it. thanks for the warning. what an idiotic concept

[fredrikaverpil]

Perhaps Mason could provide the parsers and Neovim would provide the queries, similar as to how Helix does it: https://github.com/helix-editor/helix/blob/master/runtime/queries - but then maybe in a separate repo, like neovim/nvim-lspconfig, where Mason provides the LSPs and Neovim provides the LSP configs.

I think the current/archived nvim-treesitter/nvim-treesitter was doing way too much.

[luisdavim]

There's this https://github.com/romus204/tree-sitter-manager.nvim, but I do think that having a repo in the neovim org for the queries, something like neovim/treesitter-queries, and mason to install the parsers, would be ideal.

Maybe we should open an issue about it in neovim.

[williamboman]

Looking into this right now, should be a very good fit tbh and something I've wanted to do for a long time. I'm far from a treesitter expert so I'm not entirely sure how to navigate certain things like queries.

I've only sampled a few treesitter source repos but most of them seem to provide queries themselves, and projects like nvim-treesitter and Helix are just vendoring these without any modifications (there's slight diffs but I assume this is because they've drifted apart)? If no, does anyone know how these have been maintained in nvim-treesitter and by whom?

[fredrikaverpil]

@williamboman I actually don't know the details but my understanding is that the nvim-treesitter queries have been extended with Neovim specifics. The source of truth for Neovim queries lies in https://github.com/nvim-treesitter/nvim-treesitter/tree/main/runtime/queries
I guess you can view the history for that folder to get an idea of who has been maintaining them: https://github.com/nvim-treesitter/nvim-treesitter/commits/main/runtime/queries

I would take a guess that regular users realize that a parser supports something new or requires a change in the queries and they open a PR and the maintainers of nvim-treesiter have been reviewing the change.

Anyway, I don't think that Mason should start in that end (with queries) but instead try to help solve the parser installation story. My understanding is that all parsers should be able to build by running the tree-sitter CLI in the respective git repo (with tree-sitter build). But each parser might require a toolchain which may differ from parser to parser.

[luisdavim]

I agree with @fredrikaverpil but if it is true that queries are just vendored and not modified with neovim specific requirements, it would make sense for Mason to help pulling them...

[kuator]

I agree with @fredrikaverpil but if it is true that queries are just vendored and not modified with neovim specific requirements, it would make sense for Mason to help pulling them...

off-topic, but you do have vim in your surname, that's pretty rad

[luisdavim]

This seems like a nice approach: https://github.com/reybits/ts-forge.nvim

It doesn’t seem to require vendoring the queries, I haven't tried it out yet, so I might be missing something.

What I would love to see:

• mason support for managing treesitter parsers and queries
• a new plugin under the nvim-treesitter github org focusing only on foldexpr and indentexpr part of the original repo.

I think most of the issues that lead to the archiving of nvim-treesitter came from the extra burden of managing parsers and queries but it would be great if the mainters could focus on the editor functionality and leave package management to dedicated package managers.