News for hackers. Stuff that matters.
Re:The Future of the Vim Project by kps on Thursday August 10, 2023 @12:29PM (#37078267)
> Why would you run an interactive command with `:!` ?

Why wouldn't you? Vi's `:!` is simple and general.

If neovim has an equivalent, it must be obscure enough that no one has mentioned it yet, and it seems to me that the obvious thing to do would be to make `:!` do it by default, and put neovim's current `:!` behaviour behind a `compatible` flag.

Re:The Future of the Vim Project by kzrdude on Thursday August 10, 2023 @01:42PM (#37079247)
That does sound kind of like a missed opportunity. Not sure why it's not like that.

The closest neovim equivalent I can think of is :term <command>

Re:The Future of the Vim Project by kps on Thursday August 10, 2023 @02:01PM (#37079563)
`:term` is much more intrusive; you can't just `:!foo` and get on with what you're doing. For one thing, you can't `:term foo` with a modified file, which is not an unusual state when you're editing.
Re:The Future of the Vim Project by kzrdude on Thursday August 10, 2023 @02:31PM (#37079920)
Using `:!` as a filter for text and running interactive commands doesn't overlap for me, so I haven't seen that as an issue.