this post was submitted on 27 Jan 2024
263 points (98.5% liked)

linuxmemes

21197 readers
70 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
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 14 points 9 months ago* (last edited 9 months ago) (6 children)

    It’s easy.

    Escape to exit edit mode : to prefix a command
    q to quit
    ! to confirm

    Now emacs… those people are crazy.

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

    ! = Force

    Meaning quit without saving. If no changes have been made, you can :q and that will work. If you've fumbled and made any change to the file, you'll need the ! to get it to quit without saving.

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

    with Emacs you're never out of Control

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

    Asking someone to quit emacs when they never tried before is a great method to generate random strings for a secure password.

    [–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (2 children)

    I've always preferred vi commands, they make sense and are mostly abbreviations or regex, all the other editors have the strangest commands...

    To write and quit in vi :wq

    To write and quit in nano: ctrl-o, confirmation dialog about tmp files, ctrl-x, confirmation dialog about exiting... weird feeling that I didn't actually save the file... reopen, okay it saved, ctrl-x, confirmation dialog, weird feeling that I accidently edited the file...

    [–] [email protected] 0 points 9 months ago

    I used nano for years until I forced myself to learn the basics of vi(m), now whenever something opens nano by default it annoys me and I immediately change the editor to vim 😂

    [–] [email protected] -1 points 9 months ago

    Yeah, like Word, you open it, don't change anything, close, "Do you want to save changes?"... WTF 🤨.

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

    I used emacs when I first started programming because it was what my dad showed me and I always thought it was easier than vim. Then I used a bunch of other things for a while and mostly use vim now and whenever I try to use emacs I am so confused because it makes so much less sense than vim after actually using both

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

    You could always use emacs with evil-mode to have vim key bindings

    [–] [email protected] 3 points 9 months ago* (last edited 9 months ago)

    Evil mode, I like that 🤣🤣🤣.

    [–] [email protected] 0 points 9 months ago

    For me vi was my first experience with it.

    So yeah, I think it’s often about what you’re used to