Neovim 0.12.0

#1

Post by pawelgrzybek » Sun, Mar 29, 2026, 5:39 PM UTC

Re: Neovim 0.12.0

#2

Post by benrutter » Sun, Mar 29, 2026, 6:22 PM UTC

Always interesting when a project stays 0 ver for so long- anyone close to the project know what would be considered significant enough for a "v1" release?

Re: Neovim 0.12.0

#3

Post by mi_lk » Sun, Mar 29, 2026, 6:27 PM UTC

> - d21b8c949ad7 pack: add built-in plugin manager `vim.pack

Can someone try to sell me this over lazy.nvim? I asked Claude to convert lazy config to pack and I was not happy with it because how verbose it turned out

Re: Neovim 0.12.0

#4

Post by nicebill8 » Sun, Mar 29, 2026, 6:27 PM UTC

benrutter wrote: post #2

Always interesting when a project stays 0 ver for so long- anyone close to the project know what would be considered significant enough for a "v1" release?

Possibly never: https://0ver.org/

Re: Neovim 0.12.0

#5

Post by suby » Sun, Mar 29, 2026, 6:29 PM UTC

benrutter wrote: post #2

Always interesting when a project stays 0 ver for so long- anyone close to the project know what would be considered significant enough for a "v1" release?

There is a roadmap and github issue tracking what is needed for 1.0.

https://github.com/neovim/neovim/issues/20451

https://neovim.io/roadmap/

Re: Neovim 0.12.0

#6

Post by c-hendricks » Sun, Mar 29, 2026, 6:31 PM UTC

mi_lk wrote: post #3

> - d21b8c949ad7 pack: add built-in plugin manager `vim.pack Can someone try to sell me this over lazy.nvim? I asked Claude to convert lazy config to pack and I was not happy with it because how verbose it turned out

I'm assuming there will be something like lazy.nvim built on top of vim.pack. Some of the conventions might go away (ie constantly calling `.setup`).

Re: Neovim 0.12.0

#7

Post by c-hendricks » Sun, Mar 29, 2026, 6:33 PM UTC

I unintentionally ran the main branch when testing some changes and a lot of my config broke (mostly around LSPs, CodeCompanion was much slower streaming its responses) so might wait a bit before upgrading.

Re: Neovim 0.12.0

#8

Post by kps » Sun, Mar 29, 2026, 6:33 PM UTC

benrutter wrote: post #2

Always interesting when a project stays 0 ver for so long- anyone close to the project know what would be considered significant enough for a "v1" release?

Maybe when `:!` works the way vi does and POSIX says it must.

Just kidding, that will never happen.

Re: Neovim 0.12.0

#9

Post by brcmthrowaway » Sun, Mar 29, 2026, 6:34 PM UTC

I'm using VIM - Vi IMproved 9.1. What am I missing?

I'm kind of desperate to switch. Getting massive FOMO from colleagues using VS Code. But I really like using the keyboard to navigate. What should I do?

Does NeoVim support Claude Code?

Re: Neovim 0.12.0

#10

Post by wasabi991011 » Sun, Mar 29, 2026, 6:38 PM UTC

brcmthrowaway wrote: post #9

I'm using VIM - Vi IMproved 9.1. What am I missing? I'm kind of desperate to switch. Getting massive FOMO from colleagues using VS Code. But I really like using the keyboard to navigate. What should I do? Does NeoVim support Claude Code?

If it's just using the keyboard that's holding you back from VSCode, you'll be pleased to know it has plenty of its own shortcuts, as well as a "VIM navigation" mode you can turn on.