Samuel Lawrentz | nvim-treesitter Was Archived. Here's What You Actually Need to Do.
samuellawrentz.com
nvim-treesitter got archived on April 3. If you're on Neovim 0.12, here's the exact config changes to make - and what you can safely ignore.
    • naeap@sopuli.xyz
      11·
      13 days ago

      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.devEnglish
        4·
        12 days ago

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

        Not sure I’d buy that line of thought.

  • SinTan1729@programming.devEnglish
    31·
    12 days 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.