@kasdeya For the record, it seems https://github.com/nvim-treesitter/nvim-treesitter has gone into archival mode after a discussion that referred to 0.12 being some kind of a requirement? I don't really understand this fully, but I'm not a neovim user either. Maybe you can make more sense out of it, knowing the ecosystem a little better. Or whether that plugin specifically even applies to you.

@fargate @kasdeya that's a pretty insane update if I've ever seen one... So the maintainer gave up on the project?

@fargate oh wow that sucks - I’ve been relying on this plugin for a while and I don’t really know how to replicate its functionality in any other way. as far as I can tell there aren’t even any up-to-date tutorials for how to do that, since details like this about neovim change so often

it kinda makes me wish that I had stuck with regular Vim, to be honest. I wonder if Vim has LSP support these days

thank you for finding this btw! it’s hard to say whether this is related or not, but it definitely helps a lot for me to know

@shijikori @kasdeya It would appear so, based on the exchange of messages in the discussion. Then again, they were being told to do that and already seemed stressed so I can't exactly fault them. Do take these musings with a grain of salt though, for as I mentioned I'm not really in on the neovim ecosystem. This is just something that I happened to catch on to in my fedi feed.

@kasdeya @fargate yeah. Can confirm, VIM does have LSP support.

I personally use vim-lsp( https://github.com/prabirshrestha/vim-lsp ) . If you like, I can link you to my VIM config for you to edit.

@ilobmirt @fargate ooh thank you! I might take you up on that at some point. it’s going to be a massive pain to switch because I have some fairly complex workflow stuff installed in neovim, but honestly if neovim keeps spontaneously breaking itself then I might just have to