4 ms·

Maybe when `:!` works the way vi does and POSIX says it must. Just kidding, that will never happen.

• markrian 6mo ago
  What are referring to, out of interest? Does this apply just to nvim, or vim as well?
  • PhilipRoman 6mo ago
    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 6mo ago
    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.
• flexagoon 6mo ago
  vi compatibility is explicitly a non-goal for neovim https://neovim.io/charter/ https://neovim.io/charter/
• nixpulvis 6mo ago
  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 https://github.com/neovim/neovim/issues/35258 The interactive issue: https://github.com/neovim/neovim/issues/1496 https://github.com/neovim/neovim/issues/1496 I really just want a, do the old thing setting. It was simpler and worked better.
  • konfekt 6mo ago
    :Silent [0] is an effort to work similarly in Neovim to Vim's `:!` [0] https://gist.github.com/Konfekt/8e484af2955a0c7bfe82114df683ce0f https://gist.github.com/Konfekt/8e484af2955a0c7bfe82114df683...