Obviously my personal bias, but it's emacs I can never remember how to exit from.
Me too. I once helped organize talks at my school, and helped with bringing Richard Stallman to give a talk one time. I was a vim user, but I did a little bit of prep and refreshed my emacs memory etc. So we're setting up the room for the talk, and we're talking a bit, and some people start to arrive. He asks one if they've ever used emacs, she says no, so I said, "we should start an emacs tutorial here, we can teach…
Helping a Million Developers Exit Vim
31–40 of 489 posts
Re: Helping a Million Developers Exit Vim
#32I'm somewhat amazed but mostly amused that the Vim developers care so little about user experience that they continue to ignore that people have trouble with exiting their tool and refuse to adapt to a more expected convention for exiting it.
Vim has a steep learning curve and making that one thing easier isn't going to make that curve any easier to climb. Powerful tools require documentation and looking up how to quit is the first task of many to use any of vim's power. Not everything has to be easy to use, some things benefit from not being obvious.
That said, as others have pointed out, the vim developers can't really be blamed here as it's just a very hard problem. There isn't a common convention, and vim already goes above and beyond to try and educate users on how to get out. People ending up on this SO question just seem unwilling to read.
Re: Helping a Million Developers Exit Vim
#33I barely use any Vim, but I'm more confused about there being some hidden complexity in exiting Vim that I'm not aware of. Isn't it just... [Esc] :wq ...or... [Esc] :q! ...depending if you want to save the current document or not?
No, it really is that easy. If you try to -c, the program even tells you to use :q It's just become a meme at this point.
Edit: ah quit foreground process, ignore me
Re: Helping a Million Developers Exit Vim
#34I'm somewhat amazed but mostly amused that the Vim developers care so little about user experience that they continue to ignore that people have trouble with exiting their tool and refuse to adapt to a more expected convention for exiting it.
Which would be?
Re: Helping a Million Developers Exit Vim
#35Anecdotally, would get stuck in Vim having thought that the override command was :!q instead of :q!...
Re: Helping a Million Developers Exit Vim
#36I barely use any Vim, but I'm more confused about there being some hidden complexity in exiting Vim that I'm not aware of. Isn't it just... [Esc] :wq ...or... [Esc] :q! ...depending if you want to save the current document or not?
Re: Helping a Million Developers Exit Vim
#37Earlier quoted context omitted.
It literally everytime you boot the first screen tells you how to quit and get help. So..read the screen that comes up Everytime? If you try Ctrl c it tells you it's :q.
> developers are often dropped into Vim from a git command or another situation where they didn’t expect to be, and they run into it infrequently enough to forget how they solved it last time. So the first screen doesn't help in this situation The sort of developers who get stuck in Vim are not the ones who are using it intentionally
Re: Helping a Million Developers Exit Vim
#38I'm somewhat amazed but mostly amused that the Vim developers care so little about user experience that they continue to ignore that people have trouble with exiting their tool and refuse to adapt to a more expected convention for exiting it.
> refuse to adapt to a more expected convention for exiting it. Which would be?
Re: Helping a Million Developers Exit Vim
#39Obviously my personal bias, but it's emacs I can never remember how to exit from.
Pretty straightforward.
Re: Helping a Million Developers Exit Vim
#40 +z
kill -9 %1