this post was submitted on 10 Dec 2023
688 points (95.5% liked)

linuxmemes

21219 readers
182 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
    poopsmith
    zephyr
    rtxn
    688
    why exit when you can do everything inside (discuss.tchncs.de)
    submitted 11 months ago by [email protected] to c/linuxmemes
    75 comments fedilink hide all child comments
     

    as I'm going through the process of learning vim, I'm discovering newfound powers. one of them being to execute commands from vim itself.

    below examples might better explain some of them:

    1. want to see what files are in current directory? enter command mode(by typing :) and follow it by a bang(!). then do ls like you'd do in a terminal and press enter. this is not limited to just ls. you can enter any command that you can enter in terminal. for example: :! uname --operating-system (which will output GNU/Linux :))

    2. so you want to quickly save just a certain part of your file into another file? just select everything you need by entering visual mode(v) and do :w filename(actual command you'll see would be '<,'>:w filename). verify it using 1.(i.e., :! cat filename.

    3. want to quickly paste another file into current one? do :r filename. it'll paste its contents below your cursor.

    4. or maybe you want to paste results of a command? do :r !ls *.png.

    vim is my ~ sweet ~ now. make it yours too.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 5 points 11 months ago (1 children)

    I was forced to learn the vim basics. Mainly because I really started with dd-wrt, which I used on my Linksys WRT54GL.

    The image was too small to package anything fancy in it, like nano or something, but vi (or vim, I forget) was included. So when I needed to check something over ssh at the command prompt, vim was my only choice.

    My skills in vim have not expanded beyond the basics. Getting into edit mode, exciting edit mode, saving, quitting.... Mostly.

    I don't spend a lot of time editing files in the CLI, so I haven't needed any more than I already know. Now, when faced with a Linux cli, and needing to check/edit the contents of a file, my go to, is vim. It's pretty much on every system, and it works perfectly fine for what I need to do 99.99% of the time. I like vim, it's been there for me through thick and thin, and helped me out of some serious jams. I won't hate on nano (or any other cli file editor), they all have their pros and cons.

    Use what you like.

    [–] victorz 6 points 11 months ago (1 children)

    Getting into ~~edit~~ Insert mode

    I'll admit, I took the rage bait.