5 ms·
Ok, so anyone with any terminal experience but no vim experience would press <ctrl>-c. Then, the program tells them "Type :quit<Enter> to exit Vim" And if t
by tcoff91 9y ago
Ok, so anyone with any terminal experience but no vim experience would press <ctrl>-c.
Then, the program tells them "Type :quit<Enter> to exit Vim"
And if the user is capable of reading, they shouldn't have any problem.
If they don't know about ctrl-c, they shouldn't be using a terminal editor.
- dsp1234 9y agoE37: No write since last change (add ! to override)
- zero_iq 9y agoTry actually following those instructions. They don't work. There is a step missing, and you may get warnings even if you know to hit escape first.
- Gracana 9y agoYou don't have to hit escape, ctrl-c puts you in normal mode.
- Bartweiss 9y agoIf vim opens and that's the first thing you try, then it'll work, yeah. But if you've typed anything, this won't quite work. <ctrl> c will take you out of insert mode, but won't offer any prompt. <ctrl> c again will bring up the quit prompt, but that's not intuitive the way doing it the first time is. And if you type the wrong thing after the first <ctrl> c, you'll break back into insert mode and have to take another run at it. I remember getting stuck in vim because git bash uses it as a default editor. It happened when I forgot to enter a commit message, which meant that I started typing a commit message and thereby lost the useful prompt when I went to quit. edit: per another thread, this gets far worse if you don't realize the ':' is active and not a prompt to "type: quit". That error sets off a maze that will never show you the prompt again to find your mistake.