Why is this such an issue? It is no harder exiting vim than it is exiting plain old vi, nvi or any other vi clone. In fact, the very same keystrokes that you use for exiting vi can be used in vim as well.
Stack Overflow: Helping One Million Developers Exit Vim (2017)
11–20 of 149 posts
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#12kill -9 `pidof vim` Also, whoever decided to have vim as the default editor in the windows port of git.. this is brain damaged . Just use notepad already!
Given that notepad only supports unix newlines since a few months ago, I can see why that one wasn't the default
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#13EDIT: I notice now that it has a “Type :q to exit.” I never noticed that before, and I use Vim most days, so I can see how others might miss it too.
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#14This is probably the #1 problem with Unix-based systems in general for new users. There are so many ways to exit a command prompt depending on the application! Off the top of my head: Ctrl+D, q, :q, exit, quit(), Ctrl+C, Ctrl+X. Countless times have I been locked in an application and needed to cycle through those memorized commands to escape. Imagine doing that as a newbie.
ctrl+d is the most dangerous kind! Since that one can also exit the terminal itself. gdb takes, depending on the situation, one time ctrl+d or two times ctrl+d to quit. It's a trap! So since gdb usually takes two times, muscle memory learns two times, but then in that rare instance where it required it only once... logged out of ssh :(
In zsh: setopt ignore_eof
In ksh: set +o ignoreeof
In tcsh/csh: set ignoreeof
Normally I just do this for login shells, so I can quickly exit out of subshells.
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#15Hot take: Vim should include a simple “Type :qa! to quit” line in its startup message. Something makes me think it would clear up a lot of confusion for first time users. EDIT: I notice now that it has a “Type :q to exit.” I never noticed that before, and I use Vim most days, so I can see how others might miss it too.
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#16When I got stuck every time in neovim's terminal - fixed it by adding the shortcut into statusline (there was empty space anyway).
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#17Hot take: Vim should include a simple “Type :qa! to quit” line in its startup message. Something makes me think it would clear up a lot of confusion for first time users. EDIT: I notice now that it has a “Type :q to exit.” I never noticed that before, and I use Vim most days, so I can see how others might miss it too.
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#18Hot take: Vim should include a simple “Type :qa! to quit” line in its startup message. Something makes me think it would clear up a lot of confusion for first time users. EDIT: I notice now that it has a “Type :q to exit.” I never noticed that before, and I use Vim most days, so I can see how others might miss it too.
Really it should be "Type :q to exit"
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#19Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#20Earlier quoted context omitted.
Given that notepad only supports unix newlines since a few months ago, I can see why that one wasn't the default
Sure, why not something like pico / nano? Seems more friendly to occasional users, who are the people most likely to hit the default.
Didn't think so