5 ms·

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 qu

by sirfz 9y ago

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.

ChuckMcM 9y ago
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.
- spathi_fwiffo 9y ago
  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.
  - LoSboccacc 9y ago
    Speaking of which, Control-s is much dangerous to neofites
icc97 9y ago
You get a prompt if you try to exit and you haven't written the buffer to file
- khedoros1 9y ago
  It does print a message, but doesn't prompt you for a response. I think that's the distinction that was being made.
- kevhito 9y ago
  Not in (my) vim you don't. You get: > E37: No write since last change (add ! to override)
  - icc97 9y ago
    Yeah - I figured that was as close as Vim came to a prompt It is prompting you to add a !
    - JdeBP 9y ago
      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. (-:
- sirfz 9y ago
  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.
vhost- 9y ago
You can get vim to prompt you to confirm changes with `:%s/foo/bar/gc` where c is "confirm".
flukus 9y ago
Ever tried spacemacs? Creating a tab feels like playing 20 questions.

by sirfz 9y ago

ChuckMcM 9y ago

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.

spathi_fwiffo 9y ago
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.
- LoSboccacc 9y ago
  Speaking of which, Control-s is much dangerous to neofites

icc97 9y ago

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

khedoros1 9y ago
It does print a message, but doesn't prompt you for a response. I think that's the distinction that was being made.
kevhito 9y ago
Not in (my) vim you don't. You get: > E37: No write since last change (add ! to override)
- icc97 9y ago
  Yeah - I figured that was as close as Vim came to a prompt It is prompting you to add a !
  - JdeBP 9y ago
    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. (-:
sirfz 9y ago
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.

vhost- 9y ago

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

flukus 9y ago

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