this post was submitted on 28 May 2024
362 points (94.6% liked)

linuxmemes

21160 readers
1601 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    top 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 56 points 5 months ago (4 children)

    Bought a new computer, threw the old one out.

    [–] [email protected] 15 points 5 months ago

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

    [–] [email protected] 10 points 5 months ago

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

    [–] [email protected] 5 points 5 months ago

    This is the way.

    [–] [email protected] 3 points 5 months ago

    The Apple approved way of exiting vim

    [–] [email protected] 23 points 5 months ago (2 children)

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

    [–] [email protected] 13 points 5 months ago (2 children)

    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] 7 points 5 months ago (1 children)

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

    [–] [email protected] 2 points 5 months 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 5 months ago

    Look at Mr. Bigshot here reading instructions!

    [–] [email protected] 7 points 5 months ago (1 children)

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

    [–] [email protected] 3 points 5 months ago (1 children)

    I can't deal with nano hotkeys

    [–] [email protected] 2 points 5 months ago (1 children)
    [–] [email protected] 3 points 5 months ago

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

    [–] [email protected] 17 points 5 months ago (1 children)

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

    [–] [email protected] 2 points 5 months ago

    Literally facerolled vim, nice

    [–] [email protected] 12 points 5 months ago (1 children)

    "killall vim" in another terminal tab

    [–] [email protected] 4 points 5 months ago

    who needs another tab

    :!killall -9 vim

    [–] [email protected] 12 points 5 months ago* (last edited 5 months ago) (4 children)

    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 5 months 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 5 months 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] 11 points 5 months ago* (last edited 5 months ago) (1 children)
    [–] [email protected] 5 points 5 months ago

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

    [–] [email protected] 8 points 5 months ago

    hold button to restart computer

    [–] [email protected] 8 points 5 months ago (2 children)

    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 5 months ago* (last edited 5 months ago) (1 children)

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

    [–] [email protected] 2 points 5 months ago (1 children)

    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 5 months ago

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

    [–] [email protected] 7 points 5 months ago (1 children)
    load more comments (1 replies)
    [–] [email protected] 7 points 5 months 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] 6 points 5 months ago

    Reinstalled Linux

    [–] [email protected] 5 points 5 months 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 5 months ago

    pull the computer cord out of the wall

    [–] [email protected] 5 points 5 months 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] 5 points 5 months ago

    why'd ya make it weird, OP

    [–] [email protected] 4 points 5 months ago (1 children)
    [–] [email protected] 4 points 5 months ago

    then kill %1

    [–] [email protected] 3 points 5 months ago

    control-z, kill %1

    [–] [email protected] 3 points 5 months ago* (last edited 5 months ago) (1 children)

    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 5 months ago
    [–] [email protected] 2 points 5 months ago
    [–] [email protected] 2 points 5 months ago (1 children)

    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 5 months ago (1 children)

    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!

    [–] [email protected] 2 points 5 months ago (1 children)
    load more comments (1 replies)
    [–] [email protected] 2 points 5 months ago

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

    [–] [email protected] 2 points 5 months ago

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

    [–] [email protected] 2 points 5 months 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 5 months ago (1 children)

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

    load more comments (1 replies)
    [–] [email protected] 2 points 5 months 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 ›