this post was submitted on 21 May 2025
500 points (99.0% liked)

linuxmemes

25025 readers
1496 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Shipgirlboy@sh.itjust.works 17 points 1 day ago (2 children)

    I just load bash.history in Kate or whatever and ctrl-f the command, copy the line, insert that in the terminal, adapt if necessary and go. Unless it's one of the last ten or so I used, then it's just β¬†οΈβ¬†οΈβ¬‡οΈβ¬‡οΈβ¬…οΈβž‘οΈβ¬…οΈβž‘οΈπŸ…±οΈπŸ…°οΈ

    [–] kernelle@0d.gs 8 points 1 day ago (5 children)

    history | grep

    I like seeing different usages

    [–] fmstrat@lemmy.nowsci.com 5 points 1 day ago (1 children)

    Use control r, and press control r repeatedly after the first find. It will cycle through every result.

    [–] kernelle@0d.gs 2 points 1 day ago

    Yeah that's what I'm trying to avoid, using grep displays all of my options at once.

    [–] WhyJiffie@sh.itjust.works 4 points 1 day ago

    also, put a space before history so the useless searches don't end up in the history

    [–] Bo7a@lemmy.ca 2 points 1 day ago

    I alias h to history | grep

    [–] Shipgirlboy@sh.itjust.works 1 points 1 day ago (2 children)

    I'm too brain lazy to look up how to properly use grep

    curl cht.sh/grep

    [–] kernelle@0d.gs 3 points 1 day ago* (last edited 1 day ago) (1 children)

    You can use regular strings! Can't tell you how often* I use:

    history | grep docker
    

    TIL history is a thing (I will have forgotten everything about it about 10seconds after closing this tab)