Neovim

2799 readers

16 users here now

founded 2 years ago

MODERATORS

erlingur@programming.dev

howarddo@programming.dev

lung@lemmy.world

nvim-treesitter Was Archived. Here's What You Actually Need to Do. (samuellawrentz.com)

submitted 1 day ago by codeinabox@programming.dev to c/neovim@programming.dev

4 comments fedilink hide all child comments

top 4 comments

sorted by: hot top controversial new old

[–] FiskFisk33@startrek.website 10 points 1 day ago* (last edited 1 day ago) (1 children)

What happened?

edit: never mind, i should learn to read the fucking article hah

[–] naeap@sopuli.xyz 11 points 1 day ago (1 children)

Had the same question, until I've read your comment

For everyone else with the same thought:

Quick context: Neovim 0.12 (released March 29) ships built-in treesitter support, a native plugin manager, and native LSP completion. The nvim-treesitter maintainer had been rewriting the plugin to require 0.12 - and documented this clearly. Users kept demanding backward compat with 0.11. Maintainer burned out and archived it. The Hacker News thread sided overwhelmingly with the maintainer. Hard to disagree.

[–] soc@programming.dev 4 points 1 day ago

The Hacker News thread sided overwhelmingly with the maintainer. Hard to disagree.

Not sure I'd buy that line of thought.

[–] SinTan1729@programming.dev 2 points 23 hours ago* (last edited 23 hours ago)

I've been thinking about moving away from nvim-treesitter for this. There seem to be some alternatives already, like tree-sitter-manager. Or I can probably just get it to work without any plugins.

The only thing that I'm worried about are the features provided by nvim-treesitter-textobjects. Has anyone been able to replicate those in native neovim, or even using some other plugin that's not dependent on nvim-treesitter?

Edit: There seems to be some interesting recent development.