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?

▲

suby 5 hours ago | parent | next [-]

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/

▲

nicebill8 5 hours ago | parent | prev | next [-]

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

▲

kps 5 hours ago | parent | prev | next [-]

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

Just kidding, that will never happen.

▲

flexagoon 4 hours ago | parent | next [-]

vi compatibility is explicitly a non-goal for neovim

https://neovim.io/charter/

▲

markrian 4 hours ago | parent | prev [-]

What are referring to, out of interest? Does this apply just to nvim, or vim as well?

	▲	PhilipRoman 4 hours ago \| parent \| next [-]
		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.
	▲	djb-at-durable 4 hours ago \| parent \| prev [-]
		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.

▲

saint_yossarian 4 hours ago | parent | prev [-]

AFAIK it's mostly about stabilizing the RPC API and Lua stdlib:

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