4 ms·
No, it really is that easy. If you try to <ctrl>-c, the program even tells you to use :q It's just become a meme at this point.
by tcoff91 9y ago
No, it really is that easy.
If you try to <ctrl>-c, the program even tells you to use :q
It's just become a meme at this point.
- jayflux 9y agoBut why would i be pressing <ctrl>-c in the first place if i don't know any Vim commands? Edit: ah quit foreground process, ignore me
- tcoff91 9y ago<ctrl>-c is not a vim command. It's a universal terminal command. <ctrl>-c is how you kill the foreground process in bash, zsh, sh, windows command line, etc... If you don't know about <ctrl>-c you shouldn't be attempting to use a terminal based editor to begin with. Vim can't be blamed for people not knowing how to use a terminal.
- zeptomu 9y agoBecause it is the standard command to kill (i.e. send SIGINT) running programs in a terminal? E.g. ping, top, etc. all quit using Ctrl-C.
- masklinn 9y ago> If you try to <ctrl>-c, the program even tells you to use :q And then you do and it helpfully adds ":q" to the buffer. You're still in vim.
- splawn 9y agoIf you hit ctrl-c then you are no longer in insert mode (ctrl-c acts like esc for some reason), so no, it won't add anything to the buffer and ":q" will get you out. I don't blame people for being confused though.. I remember getting stuck in vim all the time back in the day because of a default $EDITOR value.