Re:Neovim 0.12.0
by benrutter on Sunday March 29, 2026 @02:22PM
(#47565709)
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?
[ Parent
| on HN ]
There is a roadmap and github issue tracking what is needed for 1.0.
Possibly never: https://0ver.org/
Re:Neovim 0.12.0
by Night_Thastus on Monday March 30, 2026 @12:45PM
(#47576652)
I don't really get the point of this. If the 0 never changes to anything else, then effectively it serves no purpose and shouldn't exist. Some people even refer to software that way. Sometimes something like React 0.82 might be just called "React 82", and effectively it's 82.X in practice.
Re:Neovim 0.12.0
by saint_yossarian on Sunday March 29, 2026 @03:31PM
(#47566390)
AFAIK it's mostly about stabilizing the RPC API and Lua stdlib:
Maybe when `:!` works the way vi does and POSIX says it must.
Just kidding, that will never happen.
What are referring to, out of interest? Does this apply just to nvim, or vim as well?
Re:Neovim 0.12.0
by PhilipRoman on Sunday March 29, 2026 @03:09PM
(#47566157)
In Vim, :! cleans up the tty context and hands it off to the child program, to do whatever it wants, you can open any TUI program and it will work as expected.
In Neovim, :! just uses a plain pipe. Actually I believe GVim has the same problem. Since both Vim implementations now have a built in terminal handling stack anyway, I wonder if that could be used to unify the behavior.
Re:Neovim 0.12.0
by djb-at-durable on Sunday March 29, 2026 @03:11PM
(#47566185)
Just nvim. Neovim runs :! commands non-interactively, capturing the output in a pipe. vim, on the other hand, suspends itself and runs the command in an external shell.
This isn't a problem, really, for non interactive commands, but causes issues with interactive ones. I personally prefer vim's approach, though not enough to abandon neovim.
vi compatibility is explicitly a non-goal for neovim
Preach! I tried to point this out in the Neovim discord once and was basically told to pound sand. Very frustrating.
My initial issue: https://github.com/neovim/neovim/issues/35258 The interactive issue: https://github.com/neovim/neovim/issues/1496
I really just want a, do the old thing setting. It was simpler and worked better.
:Silent [0] is an effort to work similarly in Neovim to Vim's `:!`
[0] https://gist.github.com/Konfekt/8e484af2955a0c7bfe82114df683...