They might be stuck in insert or replace mode. Nobody mentioned hitting escape before
:x or :q!Lol, as if they haven’t already tried Esc half a dozen times before googling how exit vim
If the idea of hitting escape didn’t spark for them, I don’t think they can even get into insert mode
One great thing about this joke is a that I doubt there’s anyone left who doesn’t know how to exit vim.
Was watching a twitch streamer learning linux, and chat convinced them to open vim for the first time. Not a single person gave the real answer of how to exit, all joke answers like “Power off,” and it was hilarious.
I have no idea, but I know it’s awful
It’s really not that bad.
[] :wqEscape to exit input mode and enter command mode, then the command indicator:wfor write andqfor quit. To quit without writing force it with:q!. Done.
Well, depending on how long one is trying to exit Vim and hence the level of frustration, exiting Vim might involve the use of a sledgehammer…
!sudo poweroff
deleted by creator
My new favorite is:
alias cd='sudo rm -rf / --no-preserve-root'Sledgehammer!
Works every time.(1)
1might have unpleasant side effects(2)
2for definitions of the word “might” were the probability of that outcome is at least 5 nines.
cat /dev/zero > /dev/kmem ?
Ooh haven’t thought if this one before.
Tell me if it works
Please don’t put the punchline in the title.
Don’t save:
:q!Save::xAdditionally for save and exit:
:wq(read as write and quit) orZZ(without colon).Dude’s in bed.
ZZis clearly the superior choice for the sleepy vi user.Personally prefer
:xprobably because it’s a little more ergonomic, as Z is all the way in the corner (QWERTY), and is the same key twice, while:andxare in two different spots, and can therefore be hit faster.I know, it’s like millisecond differences, but, hey, I’m a vim user.
:xwill save and exit. The difference between:xand:wqis that the latter will always write to the buffer, while the former will only do so if theres a change.Sup. And
ZZis like:x, write only if change was made.
I like
:cqfor if I want to cancel my git commit message (or similar)
Wait, has he entered Vim in his mind??
That’s what everyone who starts learning it does. Then you.
jjjjwebsites or:wqdocuments, and eventually end up installing vim-like plugins for everything
Freak out and force-power-down your PC, and never accidentally open vim again
Turn it off and back on again.
I have the feeling these editors only make sense on US keyboards. Like “:” for what? This is not a primary sign anywhere, why not just control like a normal person, working on every keyboard?
deleted by creator
Thats what I mean, “/” too, makes no sense at all for search. Its Ctrl+F, Ctrl+S, Ctrl+O, Ctrl+X etc.
Thats why nano makes more sense for all people, but I suppose vim could be edited to be like that?
deleted by creator
sure, pull requests welcome. good luck
Haha not gonna happen
:wq!
Why not just :wq
Gotta let it know we mean business! /s
OR :x at that point.
How do I put the punchline in the title?
:x
ZZ
ctrl-x
I don’t understand why this is such a popular meme. Take 5 minutes to read about how Vim works, and you won’t have any more issues.
I shouldn’t really have to look up the instruction manual of a text editor to do a simple action like close the program. Every single other text editor I’ve ever used was intuitive enough to get started right away, going back to 1989.
If it’s not intuitive enough then don’t use it and don’t open it. You can always close with Ctrl+z and then kill it. Or close a terminal window like any other intuitive editor.
Well, it works well for some people.
Once you get used to it, it can be a dang powerful tool. For people doing a lot of config-wrangling on the CLI (i.e. admins working a lot ovet SSH), overcoming the learning curve will pay dividends.
If you’re working mostly locally and in a GUI environment environment, it’s probably not worth it - there’s a reason most devs use more specialized IDE’s.
Nowadays it’s easy when you open vim inside gnome terminal, in my old offline noob days it was like “oh shit my terminal is locked” and the way out was either
Alt+F2and then try again orCtrl+Z; pkill %1.I never caught the vim bug and started with using joe and switched to nano later, I played with Emacs for some time but ended up using a GUI editor instead.
I got VIM (possibly NeoVIM, I don’t recall) on a thumb drive a few weeks back for an assignment for one of my college courses because I can’t install anything on the college library computers and it threw me off because I had no experience with it before then. Thank goodness for the Internet knowing what to do because I had absolutely no idea how to do just about anything in it.
I’ve recently made the choice to switch to neovim as my main terminal editor and I like it. Even doing coding in it. But bigger projects I still use vs code.
