for the techies: exiting vim

[cellio]

I once heard a quip that went something like this:

"I used vi for a couple years."
"Yeah, I couldn't figure out how to exit, either."

I admit that the first time I was unwittingly thrown into the vi editor (predecessor to vim), I had to kill the process from another terminal (yes, terminal). So I was amused to see this blog post today: Stack Overflow: Helping One Million Developers Exit Vim.

In the last year, How to exit the Vim editor has made up about .005% of question traffic: that is, one out of every 20,000 visits to Stack Overflow questions. That means during peak traffic hours on weekdays, there are about 80 people per hour that need help getting out of Vim.

The point of the post isn't actually to bash vim, though it humorously acknowledges the widespread problem (and c'mon, you have to do it a little). Mostly they analyze data about who is presumably getting stuck in vim, complete with charts and stuff. Enjoy.

Comments

[goljerp]

Ah, good old days. I first cut my teeth on a DEC PDP-11. We had a bunch of VT220s, some VT100s, and a lonely VT52 in a corner. And a couple of lineprinters, but I don't think they really wanted kids logging into 'em, in general. So I learned EDT. Which actually served me fairly well, as I did a bunch of my dissertation in an updated version of that (on a Decstation). But in the vi(m) / Emacs wars, I tend to firmly come down on the side of: pico. (nano?) I'm not a sysadmin; if I need to do anything more complex than just "cat >> test.txt" in a terminal, I want something simple which has the commands I need clearly labeled on the bottom.