3 ms·
When I first entered vi/vim I had no idea what it was. To know how to exit vim you first have to know that’s what you are trying to exit. I suspect at least ha
by alkonaut 8y ago
When I first entered vi/vim I had no idea what it was. To know how to exit vim you first have to know that’s what you are trying to exit.
I suspect at least half of the confusion comes from people accidentally entering vim without any intention to do so.
One of the most common examples is git that some times launches a text editor and in some conditions that might be vim.
If you are doing a “git rebase -i” for the first time in Cygwin and you never used another linux/Unix shell before (very common in Windows-only devs, which are a significant portion of devs), then being greeted by some “~” characters, a cryptic status bar and Ctrl+C doesn’t exit - then you google. You don’t even google “How to exit vim”, you google “How to exit git rebase” or similar.
Now, if you launched vim, then the story is different. Then you know what you started. You can at least know WHAT manual to read. But as I said I’m guessing a large number of those can’t leave vim had no intention to start it either.
I must have started vim hundreds of times, almost none of which were deliberate (misconfigured editors on vm’s etc). A lifelong windows user typically wants to use nano or similar.
- Cyphase 8y ago(This is a reply to the GP comment, since it got flagged while I was typing my reply.) --- > If you downvote this you're to dumb to even look stuff up on Google. What do you think the first result is when you search for how to exit Vim? > RTFM is at least 50% of what makes a good programmer. Stack Overflow is part of the metaphorical manual.
- afiori 8y agoTo add, the word quit does not even appear in the man page