44
nvim-treesitter Was Archived. Here's What You Actually Need to Do. (samuellawrentz.com)
submitted 6 months ago by to c/neovim@programming.dev
4 comments fedilink hide all child comments

all 4 comments

sorted by: hot top controversial new old
[–] 12 points 6 months ago* (2 children)

What happened?

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

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 12 points 6 months ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
    • [–] 2 points 6 months ago* (last edited 6 months 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.

  • permalink
  • fedilink
  • source
    •