361
submitted 1 month ago by [email protected] to c/[email protected]
top 50 comments
sorted by: hot top controversial new old
[-] [email protected] 55 points 1 month ago

Bought a new computer, threw the old one out.

[-] [email protected] 14 points 1 month ago

We're dangerously close to revealing the real reason I keep trying new operating systems...

[-] [email protected] 9 points 1 month ago

That's an easy fix. I had to burn my house down

[-] [email protected] 5 points 1 month ago

This is the way.

[-] [email protected] 2 points 1 month ago

The Apple approved way of exiting vim

[-] [email protected] 22 points 1 month ago

I was introduced to Linux with Vim so it's actually Nano that confuses me...

[-] [email protected] 13 points 1 month ago

The good thing about nano is that it has clear instructions for how to close it right there immediately in front of you

[-] [email protected] 6 points 1 month ago

Not if aren't familiar with control characters. Might was well be three seashells...

[-] [email protected] 2 points 1 month ago

Same, every new system that defaults to nano and throws me in here when I'm expecting vim I have to stop and remember what the characters mean right before changing it to use vim (like, seriously, I typed "visudo", not "nanosudo", why the hell would I expect it to open in anything other than vi or vim?)

[-] [email protected] 4 points 1 month ago

Look at Mr. Bigshot here reading instructions!

[-] [email protected] 7 points 1 month ago

I've always been using nano, but since I refused to ever read the docs, I'm still confused

[-] [email protected] 3 points 1 month ago

I can't deal with nano hotkeys

[-] [email protected] 2 points 1 month ago
[-] [email protected] 3 points 1 month ago

I was using a distro for a sbc recently and nano was the default visudo editor. Infuriating

[-] [email protected] 17 points 1 month ago

CTRL+face on keyboard. I guess Z got me out, but who knows.

[-] [email protected] 2 points 1 month ago

Literally facerolled vim, nice

[-] [email protected] 12 points 1 month ago* (last edited 1 month ago)

From the torrent, the deluge, the unending tidal wave of this exact meme in various formats. The "exit vim difficult" meme must constitute at least 50% of online content regarding *nix and *nix-adjacent systems. It is so stale that Slackware considers it outdated. It is the "mayonnaise is spicy" equivalent of funny. It is the white bread, picket fence stereotype of meme culture, yes offense. I'd like to say that it's beating a dead horse, but the horse is gone; its flesh has been tenderized, pulverized, and evaporated from the sum total of energy imparted by the constant beating. If the heat death of the universe were to happen tomorrow, and from the uniform vacuum energy a Boltzmann brain were to spontaneously form, it will have been already tired of this meme.

But to answer the question, it was either that, or the big

type :q<Enter> to exit

splash that appears when I open it with an empty buffer, and following its instructions.

No offense to you or your house, but I'm really tired of this meme.

[-] [email protected] 4 points 1 month ago

splash that appears when I open it with an empty buffer, and following its instructions.

That's the key to the problem, I have almost never open vim with an empty buffer, almost only used it to open files directly. Since there is no nice splash screen telling you how to exit when you use vi <your_file>, this meme happens.

[-] [email protected] 2 points 1 month ago

No offense, but I was dumb enough to wonder why they put a space before ":" and thought something must be broken. Obviously, pressing q and Enter (or typing <Enter>) also didn't work and proved to me that this editor must have crashed in a strange way.

So every time I see vim, it reminds me about my stupidity. The meme eases the pain.

load more comments (2 replies)
[-] [email protected] 12 points 1 month ago

"killall vim" in another terminal tab

[-] [email protected] 4 points 1 month ago

who needs another tab

:!killall -9 vim

[-] [email protected] 11 points 1 month ago* (last edited 1 month ago)
[-] [email protected] 5 points 1 month ago

Cuz it's kill dash nine. No more CPU time.

[-] [email protected] 8 points 1 month ago

I guess it was in the 80s, open a new xterm, ps -edaf | grep vi, kill the process, then man vi to read how to exit properly.

This is how I learnt unix, do a ls in /bin /usr/bin /etc, man every command

[-] [email protected] 7 points 1 month ago* (last edited 1 month ago)

If it was the 80s, didn't you have to feed punch cards through the mainframe first? /s

[-] [email protected] 2 points 1 month ago

Already had huge X Terminal on HP mainframe, using X11R3 and mwm etc. xeyes, xload, xbiff, xterm, it was the time!

load more comments (1 replies)
[-] [email protected] 2 points 1 month ago

Similar. I'd guess it was something like ctrl-z; ps -e vi; kill -9 procnum on a vt100 terminal.

[-] TornadoRex 8 points 1 month ago

Reinstalled Linux

[-] [email protected] 8 points 1 month ago

hold button to restart computer

[-] [email protected] 7 points 1 month ago

Long before I used vim, some dude shared a bunch of vim memes with ":q!" in them.

It was actually vi on some ye olde unix machine, but I remembered the meme and got out, searched up how to use vim, and then jumped back in to edit the file lol.

[-] [email protected] 7 points 1 month ago
[-] [email protected] 2 points 1 month ago

You say it like ^X was somehow intuitive

[-] aBundleOfFerrets 5 points 1 month ago

why'd ya make it weird, OP

[-] [email protected] 5 points 1 month ago

I guess just because how the question was laid out, I'm disqualified as I was taught how to use it the first time I used it. :P

with my first linux -system, I had an experienced friend to hold my hand while installing, configuring and usage - including vim. So, the first thing he taught me was how to exit it. This was sometime in ... 2003-ish?

[-] [email protected] 5 points 1 month ago

pull the computer cord out of the wall

[-] [email protected] 5 points 1 month ago

Probably closed the terminal emulator it was running in and opened a new one before trying to find documentation at my leisure. One of the luxuries of learning Unix commands in a graphical environment.

For a more drastic noob story, I once rebooted a computer because I couldn't get out of GWBASIC. I was familiar with QBASIC at the time and that was a lot easier to get out of if you didn't know what you were doing.

[-] [email protected] 4 points 1 month ago
[-] [email protected] 4 points 1 month ago

then kill %1

[-] [email protected] 3 points 1 month ago
[-] [email protected] 3 points 1 month ago* (last edited 1 month ago)

Honestly?

By looking up the command. It took like two seconds and that was nearly twenty years ago. And I've been using it off and on since then (only off because I've not been consistently using Linux, not because I'm using a different terminal text editor; when on *NIX, vim/vi is pretty much all I've used on the terminal)

load more comments (1 replies)
[-] [email protected] 3 points 1 month ago

control-z, kill %1

[-] [email protected] 2 points 1 month ago

A tutorial tried to get me to install emacs the other day. I guffawed in nano.

[-] [email protected] 2 points 1 month ago

North Carolina style, head to your nearest electric substation and open fire*

*Doesn't work for laptops, instead just shoot the laptop

[-] [email protected] 2 points 1 month ago
[-] [email protected] 2 points 1 month ago

I started on MacVim, so I could just use cmd+q. And by the time I used vim on the terminal I knew all about :commands

[-] [email protected] 4 points 1 month ago

That should be illegal. Any editor containing the letters vi together must not use any keys except those that can be sent over a vt100 terminal!

load more comments (2 replies)
[-] [email protected] 2 points 1 month ago

I closed the terminal, the second time I googled how to quit

[-] [email protected] 2 points 1 month ago

Shutting down my computer with the button, restarting, and installing Emacs.

load more comments (1 replies)
[-] [email protected] 2 points 1 month ago

I can't remember what I did with vim the first time I used it, but whenever I'm stuck in a cli program and want to go back to the shell, I usually tried ctrl+c first, and if doesn't work, crtl+z.

load more comments
view more: next ›
this post was submitted on 28 May 2024
361 points (94.8% liked)

linuxmemes

19717 readers
323 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS