Neovim 0.13 is still under development, but it is already shaping up to be one of the more interesting Neovim releases in a while.
  • hallettj@leminal.spaceEnglish
    3·
    21 days ago

    There are lots of substantial improvements coming! I’ll point to some points that appeal to me personally that aren’t big enough to make headline news given how much else is coming.

    Neovim also adds:

    vim.treesitter.select()

    for starting or adjusting visual selections based on syntax-tree nodes.

    AST-aware editor interactions are something I’ve really been missing since leap-ast.nvim was archived. Maybe there’s a good plugin for quick selections or text objects based on AST structure that I haven’t gotten around to trying. But I’m looking forward to built-in building blocks!

    Edit: Wow I’m dense - leap-ast was archived because Treesitter integration is now built into leap.nvim.

    Neovim now exposes a logging interface:

    vim.log

    Sounds like a quality-of-life change that will be real nice to have when you want it! I hope this will replace my uses of print(vim.inspect(...))

    There is now:

    :bcd

    for setting a buffer-local current directory.

    I’ve been surprised in the past that this wasn’t possible before.

    And finally, the :restart command to apply your updated editor config while preserving your open buffers and windows!

    • unglueclass23@programming.devOP
      3·
      21 days ago

      The new textobjects al and il are a great addition as well. Won’t need a shortcut to select the whole buffer anymore and won’t need to do 0 -> ^ -> y$

  • Maddier1993@programming.dev
    57·
    21 days ago

    At this point we need a bootcamp to setup our editors first before we have the bootcamp/course for the actual language/work we want to accomplish.

    Well, congratulations on neovim graduating the university of complexity! Emacs was the chief guest.

      • MadhuGururajan@programming.devEnglish
        11·
        13 days ago

        Huh… I was trying to make a joke like people usually do at the expense of emacs but I came across some humourless accounts. (And this is my alt… don’t be weirded out)

    • hallettj@leminal.spaceEnglish
      2·
      21 days ago

      Is there some change you’re particularly concerned about wrt to setup complexity? Lots of the changes might simplify setup because they build in functionality that previously required plugins. The LSP improvements mainly apply at the interface between LSP server and editor, not stuff that users would set up themselves. A bunch more changes are either behind-the-scenes performance improvements, or are directed at plugin authors. There are new features added. But I don’t see anything that makes set up more complicated.

      • MadhuGururajan@programming.devEnglish
        11·
        13 days ago

        Replying from my alt:

        I was trying to make a joke but seems it rubbed off the wrong way. Although I do think there’s a philosophical discussion of complexity to be had here.

        The problem with thinking “We have now simplified xyz software” is software developers have this bad habit of often assuming that the world updates to the latest and greatest version of software the moment they deploy it and they erase any semblence of past versions, shortcomings, or even workarounds that others may have deployed and trained their muscle memories on.

        Complexity actually goes up the more versions of software that are released in the world.

        You now have neovim <= 0.12, <= 0.13, 0.13 to keep in your head if someone comes to you for advice on how to setup this cool editor on their distro and they may or may not be able to upgrade to the latest version.