now that nvim-treesitter has been archived (https://github.com/nvim-treesitter/nvim-treesitter) eyes passim: (https://news.ycombinator.com/item?id=47644667, https://lobste.rs/s/jr4acs/nvim_treesitter_repository_was_archived). What now, if using nvim 0.12?
there's very little code within the actual library, the primary use case was for the configs
i think we'll end up with custom plugins/libraries for each language, which is annoying but ultimately not much worse than what we currently have
Using Neovim 0.12 just fine with the latest commit of nvim-treesitter. Keep calm. It more a 'problem' for Neovim 0.11 at the moment as the shim to make that version work was removed (accidently) when Neovim 0.12 was released. But you can still pin to a working version. Note that Neovim 0.11 is not officially supported anyway. I think the main reason that repo was archive is that too many people were hasling the maintainer and not reading any of the docs (not even the first paragraph of the readme) There were some nasty comments left in at least one GitHub discussion thread. I think that was the final straw. I empathise with the maintainer.
i looked into replacing with custom code, and i think it's gonna be more annoying that i initially thought, which is a bummer. however, everything works for now and will continue to work for a while longer. clason continues to work on both neovim and tree-sitter, so he's not taken his expertise and run away, merely stopped providing this specific plugin
Issue to upstream nvim-treesitter (in a similar way to nvim-lspconfig) https://github.com/neovim/neovim/issues/39006
I just removed nvim-treesitter from my config. Honestly, I should have done it a while back. Not a fan of :TSInstall. Now I can explicitly pin each parser plugin via Lazy.
I'm expecting it'll return soon enough. Am I very wrong?
yes lol
clason has been working on integrating certain parts into neovim and tree-sitter directly