this post was submitted on 27 Dec 2023
152 points (75.3% liked)

linuxmemes

21143 readers
1385 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] 65 points 10 months ago (9 children)

    I feel like the images should be switched.

    load more comments (9 replies)
    [–] [email protected] 50 points 10 months ago (5 children)

    If you wanna save changes: :wq

    If not: :q!

    Else: :SpanishInquisition

    [–] [email protected] 6 points 10 months ago (6 children)

    Why do so many people prefer :wq over :x?

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

    Cause I don't like to think about my x

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

    Because :wq to me means "Issue command write, followed by command quit." "Issue command x" to me means nothing in the context of vim, and ctrl + x on most systems is reserved for cutting, so it just "feels" wrong.

    load more comments (4 replies)
    [–] [email protected] 6 points 10 months ago

    Hmm, I didn't expect that last one.

    load more comments (3 replies)
    [–] [email protected] 32 points 10 months ago* (last edited 10 months ago) (2 children)

    I prefer the extremely intuitive:

    [C-R]=system("grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9")

    or

    i:!grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9[esc]Y:@"[cr]

    It just rolls off the fingers, doesn't it?

    Edit: damn it lemmy didn't like my meme because it assumes that characters between angle brackets are html tags :( you ruined it lemmy

    EDIT 2: rewrote it, just assume that square brackets are buttons not characters

    load more comments (2 replies)
    [–] [email protected] 27 points 10 months ago (3 children)

    I always get annoyed when I'm on some system and nano pops up and I need to figure out how to kill that thing.

    [–] [email protected] 29 points 10 months ago (7 children)

    Nano literally tells you all the shortcuts to your face.

    load more comments (7 replies)
    [–] [email protected] 7 points 10 months ago

    Same. As a vim user I now can't quit nano.

    [–] [email protected] 5 points 10 months ago (9 children)

    Very intuitive - Ctrl + X... unlike vim.

    [–] [email protected] 12 points 10 months ago (7 children)

    Why is Ctrl-X intuitive? Shouldn't it be Ctrl-Q (for "quit")?

    [–] [email protected] 5 points 10 months ago (4 children)
    [–] [email protected] 9 points 10 months ago (2 children)

    In most apps, Ctrl-X means "cut", not "quit". Especially when it's a freakin' text editor!

    I will grant you that it's more intuitive than vi, but that is a very, very low bar.

    load more comments (2 replies)
    load more comments (3 replies)
    load more comments (6 replies)
    load more comments (8 replies)
    [–] [email protected] 25 points 10 months ago (1 children)

    There's a button to exit vim on your pc. Just hold it 7 seconds and vim is closed. 😅

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

    it's right next to the turbo button

    [–] [email protected] 22 points 10 months ago (2 children)

    you don't need the ! when you have the w, because your changes already get saved.

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

    If anything it is dangerous as it will still exit even if changes cannot be saved.

    [–] [email protected] 6 points 10 months ago (2 children)

    Try editing a file in /etc as a regular user. It happens sometimes and you really want that warning that the write failed.

    Anyway, :x is superior. It only writes if there are changes. So, your mtime doesn't change unnecessarily.

    load more comments (2 replies)
    [–] [email protected] 19 points 10 months ago (4 children)

    :ggdGwq (please don't do this)

    [–] [email protected] 14 points 10 months ago (1 children)

    VIM Golf.... Same outcome, fewer strokes:

    %d|wq

    [–] [email protected] 6 points 10 months ago (1 children)

    you can replace wq with x

    :%d|x

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

    Only in Vim, not in Vi.

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

    E492: Not an editor command: ggdGwq

    [–] [email protected] 11 points 10 months ago (1 children)

    I use Vim daily, and i have absolutely no clue what that command would do, what would it do? Delete the document, save and quit?

    [–] [email protected] 15 points 10 months ago* (last edited 10 months ago) (2 children)

    exactly.

    gg -> go to top of document

    d -> delete (actually, it's cut, but it destroys the mnemonic)

    G -> here is a modifier to "d" and tells it do "delete until end of document"

    w -> write current state of buffer to disk

    q -> exit program

    [–] [email protected] 17 points 10 months ago (2 children)

    Actually not, binds and commands aren't the same. ggdG only works as a series of inputs, while wq only works as a command (with the colon).

    [–] [email protected] 8 points 10 months ago (1 children)

    Exactly. The colon needs to be just before the w, not at the front of the sequence...

    [–] [email protected] 6 points 10 months ago (1 children)

    And while you're at it, throw an ESC in there at the beginning, will ya?

    load more comments (1 replies)
    load more comments (1 replies)
    load more comments (1 replies)
    load more comments (1 replies)
    [–] [email protected] 13 points 10 months ago (6 children)
    <ESC>
    <CTRL>+Z
    killall -9 vim
    
    [–] [email protected] 11 points 10 months ago (1 children)

    And then sudo apt install nano

    load more comments (1 replies)
    load more comments (5 replies)
    [–] [email protected] 10 points 10 months ago* (last edited 10 months ago) (1 children)
    load more comments (1 replies)
    [–] [email protected] 9 points 10 months ago
    [–] [email protected] 5 points 10 months ago
    load more comments
    view more: next ›