Hacker News Reader

Comment by sirfz | Hacker News Reader

That looks more like emacs behavior though, vim rarely (never?) prompts the user for anything. You enter a command, you get a reaction (either an action like quits vim, or a message indicating something happened) -- which I personally prefer much more than getting annoying prompts.

View on HN

I don't disagree. And I like that vim doesn't prompt you a lot, but it is the one corner case where such prompting could be useful.

it already tells you hot to quit when you hit control-c and if you happen to be in edit mode, hitting it twice gets you the message.

if people don't notice the "Type :quit<Enter> to exit Vim" message, they also won't see the (Y/N) selection.

so, absolutely nothing gained by making this change, except making things more annoying for people who do know how to use vim.

Speaking of which, Control-s is much dangerous to neofites

You can get vim to prompt you to confirm changes with `:%s/foo/bar/gc` where c is "confirm".

You get a prompt if you try to exit and you haven't written the buffer to file

Not in (my) vim you don't. You get:

> E37: No write since last change (add ! to override)

Yeah - I figured that was as close as Vim came to a prompt

It is prompting you to add a !

It has closer things to prompts. Try editing a file when the last time around you terminated vim without giving it a chance to clean up its .*.swp file. (-:

It does print a message, but doesn't prompt you for a response. I think that's the distinction that was being made.

Actually you get a prompt when you try to save a file that has been modified in a different session or when you switch to a similarly modified buffer. But those are pretty reasonable and don't happen that often.

Ever tried spacemacs? Creating a tab feels like playing 20 questions.

Reply on news.ycombinator.com