Live data from Hacker News

Helping a Million Developers Exit Vim

stackoverflow.blog

61–70 of 489 posts

Re: Helping a Million Developers Exit Vim

#61

I 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?

ZZ also works as save and quit.

Re: Helping a Million Developers Exit Vim

#62
I can still remember sitting at a VT-220 in the college computer lab with my first Unix account (on a MIPS DECstation of all things), running emacs[1], getting stuck, and then sheepishly having to yank the power on the terminal to fix things.

[1] Would have been emacs 18.something at the time. Not sure if that predates the built-in tutorial or if I just missed it. I remember running the tutorial not long thereafter on a proper workstation where I felt comfortable I could close the window.

Re: Helping a Million Developers Exit Vim

#65

I 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?

It baffles me that it isn't just ^C like every other unix program.

Every other unix program is not an interactive editor, they don't care if stdout is a teleprinter, a physical terminal or a terminal emulator.

Re: Helping a Million Developers Exit Vim

#66
(Attribution is questionable, but as a geezer I feel the need to make sure the younger generations at least are familiar with this:)

ed is the standard text editor

Let's look at a typical novice's session with the mighty ed:

  golem> ed

  ?
  help
  ?
  ?
  ?
  quit
  ?
  exit
  ?
  bye
  ?
  hello? 
  ?
  eat flaming death
  ?
  ^C
  ?
  ^C
  ?
  ^D
  ?

  ---
  Note the consistent user interface and error reportage.  Ed is
  generous enough to flag errors, yet prudent enough not to overwhelm
  the novice with verbosity.
(As a geezer, I also have to say I really am impressed with ed in some ways, and you should never be afraid to try it when you have a specific and known edit you want to do.)

Re: Helping a Million Developers Exit Vim

#67

Earlier quoted context omitted.

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.

I think this is a poor argument. If it's the one singular thing that's frustrating this many users, that's a reason to focus on particular on fixing it somehow. You also need to take into account that most users encountering this problem are not deliberate vim learners: they ended up in vim by accident. That said, as others have pointed out, the vim developers can't really be blamed here as it's just a very hard prob…

There is a common convention, though, which is: don't use modal interfaces, modal interfaces are bad.

The problem vim has is that its UI is entirely organized around modes, which makes the "people are terrible at using modal interfaces" problem a hard one for it to cope with.

Re: Helping a Million Developers Exit Vim

#68
post #29
post #12

Earlier 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.

dev: That just typed ':q' into the text area me: Hit escape first, then :q dev: Oh, then why doesn't say escape then :q me: welp

Another thing I've seen is the person reads the text as:

"Type: quit to exit Vim"

Since the colon is used a separator such as I used it above.

Then they type "quit" and enter, which actually put them in insert mode recording "@u", with a 't' sitting in the text area.

Re: Helping a Million Developers Exit Vim

#70
post #7

The most viewed question is even more relatable: https://stackoverflow.com/questions/927358/how-to-undo-last-... You can get the top viewed questions here: http://data.stackexchange.com/stackoverflow/query/53109/ques...

My own personal top hit is:

https://stackoverflow.com/questions/2003505/how-do-i-delete-...

Pretty sure I've got the command down by now, but it's embarassing how many times I forgot the exact syntax. It was especially bad before the "--delete" syntax was introduced.

Post reply on HN