this post was submitted on 04 Jul 2023
1235 points (98.5% liked)

linuxmemes

21222 readers
80 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@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    1235
    Look, I'm lazy, okay? (lemmy.world)
    submitted 1 year ago by primaryuser@lemmy.world to c/linuxmemes@lemmy.world
    85 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] Skyler@kbin.social 7 points 1 year ago (1 children)

    This is my approach, and for those who don't know, you can use those line numbers that come back from history to rerun the command. Like if your output is something like this:

    $ history | grep tmp
  501  ls /tmp
  502  history | grep tmp

    You can run !501 and it will just re-run ls /tmp

    [โ€“] IthronMorn@sh.itjust.works 1 points 1 year ago

    Woah! I had no clue!