User: I accidentally opened vim. How do you even quit this thing?

me: that's their adoption strategy. it's Hotel California of text editors

@nixCraft CTRL X, CTRL C. Dammit, no...
@nixCraft I think it was [ESC] and at the ":" prompt type: q!
@harald_e_langner @nixCraft
and continue:
after quitting, install "nano" !
@nixCraft oh, no.. on a dark desert highway, cool wind in my hair
@ryan_oke @nixCraft in a dark data center, cool fans in my eyes
@nixCraft Years ago, when the debate raged between vi and emacs, and I was new to linux/unix i made my decision of which to use with a little test.
I opened a file in vi and emacs. the one i could exit from without looking at documentation would be the one i would use.
vi won.
@zedaardv @nixCraft I had to work to learn vi. Even with work, I could never figure out emacs.

@nixCraft

I had the same experience in school.

To this day :wq is the only Vi ( I went to school a long time ago ) command I remember.

@nixCraft @rasterweb I don't know much, but whenever I'm carefully following some installation instructions and it says "now type vim config and change these lines"... I know to use nano instead so I don't have to look up MORE instructions!
@Andrew @nixCraft I also prefer nano.
@rasterweb @Andrew @nixCraft The account of time it takes to save off and exit nano annoys me every time I try it. But then I've been using vim for decades now, so…
@fnxweb @rasterweb @nixCraft if I'm being honest, my go-to for anything more than a minor edit is xed. 😅
@Andrew @fnxweb @rasterweb @nixCraft Y'all should try micro, it's like nano but has sane hotkeys
@nixCraft 
Back at university they had a big Banner
"vi causes brain damage"
@nixCraft CTRL+Z, followed by using 'ps -A |grep vi' to get the process number of vi. Next, use the 'kill' command to get rid of that process. Proceed to 'kill -9' if it refuses to go away.
@OwenTyme @nixCraft or jobs and kill %jobnr maybe then fg %jobnr to assign cpu cycles to vi to actually quit. (Not near a cmdline so I might have a typo…)
@nixCraft you can :w any time you like but you can never :q!

@nixCraft
🤣 😂
Yes. It is like that, is it not?

The proper answer to the questions is: "Why would you want to quit vim?" 🤭

@nixCraft Dunno what you are talking about. They literally have a hard button for that…it’s called the “Power Button”
@nixCraft vim literally says how to exit in the middle of the screen when you first open it. If you can't read, text editors may not be for you.
@nixCraft only way is to reboot computer
@nixCraft Just reboot the server… and don’t do it again, #nitwit. 🤣 😘
@nixCraft Have you ever tried to quit minicom?
@nixCraft I learnt to use vi in 1988. Now, if I accidentally get nano (ie by running visudoers) I have learnt how to quit
@nixCraft Go colon queue bang yourself.
@nixCraft I watched a #NeoVIM introduction video recently where the presenter ended with... I could tell you how to quit, but then I have to kill you 😉
@nixCraft Exiting vi has gotten so much easier. In the past, I worked on multiuser shared systems, so I couldn’t just reboot it like I do now.
@nixCraft as far as I remember: hard boot. Power off and on again. Well that was vi not vim. But I guess it works with vim too...
@nixCraft The same way you quit ed & ex, duh.
@nixCraft everyone knows that the real way to quit vim is to open another terminal, find the vim pid using ps, and kill it. this was as far as UX research had advanced as of the early 90s.
@nixCraft Vim runs in kernel space. It cannot be killed. Long live Vim. ha ha ha ha.

@nixCraft

That would be emacs. I believe there are terminals I walked away from in the '80s where an emacs session is still running under my user credentials.

@nixCraft do :q! 10 times miserably, cursing yourself, hope and pray that it will close. Or open another terminal and forget about this one.
@nixCraft If you somehow happen to run the (poorly named) physics analysis application called ROOT, remember ".qqqqqq". (I forget if the "q"s past the third or fourth actually do anything, but it doesn't hurt, and your "q" key is likely otherwise sadly neglected.)
@nixCraft
This could be heaven or this could be hell
@briankrebs
@nixCraft
This flashed briefly on my screen when I opened the app, then a syndicate of toots loaded, hiding this before I got to the punchline. I had to hunt this down scrolling and scrolling, forgetting (thanks ADHD) what it even was that I was looking for so vigorously, but here it is. And it's excellent. Thank you.