this post was submitted on 04 Jul 2023
797 points (98.7% liked)

linuxmemes

21225 readers
40 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
    [–] m15otw@feddit.uk 48 points 1 year ago (6 children)

    Ctrl+R

    Then type any part of the command (filename, search string, etc)

    Ctrl+R again to cycle through the matches.

    (Best feature in bash)

    [–] p0q@sh.itjust.works 12 points 1 year ago (1 children)

    Use fzf for a more visual search.

    [–] LeanFemurs@lemmy.world 5 points 1 year ago

    This is the way.

    [–] brakenium@lemm.ee 8 points 1 year ago (1 children)

    I've been using this for a long time, never knew I could press Ctrl + R again. Thanks!

    [–] wandering_nomad@lemmy.world 8 points 1 year ago

    Ctrl + S to go the other way if you overshoot!

    [–] spoopyking@lemmy.fmhy.ml 6 points 1 year ago (1 children)

    Or history | grep 'command'

    [–] m15otw@feddit.uk 3 points 1 year ago (1 children)

    Can't just hit enter to run the one you want then, though.

    [–] rufus@lemmy.world 7 points 1 year ago

    Type: !1234 ... to run whatever history number of the command.

    [–] LucidDaemon@lemmy.world 1 points 1 year ago

    Wish I knew this sooner.

    load more comments (2 replies)
    [–] HorreC@kbin.social 22 points 1 year ago (9 children)

    control shift R, then start typing, it will search your bash history

    [–] mrmanager@lemmy.today 11 points 1 year ago (3 children)

    Hmm, normally it's just ctrl - r... Are you sure the shift is needed on your system?

    [–] lungdart@lemmy.ca 3 points 1 year ago (1 children)

    Don't forget fzf. That will really jazz up your history search!

    [–] mausy5043@lemmy.world 1 points 1 year ago (2 children)
    [–] mrmanager@lemmy.today 1 points 1 year ago

    Ok if you want to learn Linux, you need to start web searching for stuff you hear about. :)

    load more comments (1 replies)
    [–] HorreC@kbin.social 2 points 1 year ago

    you are right, I must have just learned it with a shift for some dumb reason and it stuck, thank you internet person.

    [–] med@sh.itjust.works 1 points 1 year ago

    Some variants have ctrl+r bound to something else

    [–] LobsterDog@frig.social 9 points 1 year ago (1 children)

    Is it not just Ctrl-R or is that platform dependent

    [–] count_duckula@discuss.tchncs.de 3 points 1 year ago (1 children)

    I have always used ctrl-r but I just checked and both work. TIL.

    [–] tsukassa@lemmynsfw.com 3 points 1 year ago

    Thanks for clearing up this mystery.

    [–] rikudou@lemmings.world 3 points 1 year ago

    I recommend using mcfly for that, it makes it even better.

    [–] whofearsthenight@kbin.social 1 points 1 year ago (1 children)

    Now if you had to guess how often I remember that there is a keyboard shortcut that does this, but don't remember what it is, and do remember that I can just press up 30-70 times...

    load more comments (1 replies)
    load more comments (5 replies)
    [–] ttk@feddit.de 10 points 1 year ago

    fzf masterrace

    [–] tobier@lemmy.world 9 points 1 year ago (3 children)

    This is why I switched to fish; it seems to be much smarter understanding what I want to type.

    [–] amos@lemmy.world 7 points 1 year ago (1 children)

    Yeah it's great how ctrl-r is kinda the default instead of something you have to go out of your way to use. Just start typing a command and the up arrow will only cycle through history that matches what you've typed so far.

    [–] sneeple@reddthat.com 2 points 1 year ago (1 children)

    Idk exactly what plugin it is, but zsh + oh my zsh has exactly this same thing. So hard to live without now that I'm used to it. Probably my favorite feature

    [–] notavote@lemmy.world 2 points 1 year ago (2 children)

    That is default zsh history search, pretty nice.

    load more comments (2 replies)
    load more comments (2 replies)
    [–] Aceticon@lemmy.world 7 points 1 year ago

    It's like the bus-stop-paradigm: If I wait just a bit longer and it will come. Meanwhile it would've been faster to walk.

    [–] Sketchpad01@lemmy.world 7 points 1 year ago (1 children)

    Using the history command just to find the specific IP I need to ssh to

    load more comments (1 replies)
    [–] Badland9085@lemm.ee 7 points 1 year ago

    To anyone who uses vim mode, ? lets you search through your stored command history, from normal mode ofc.

    [–] skomposzczet@vlemmy.net 6 points 1 year ago

    up, up, up, up, up, cd .., ah there it is.

    [–] Ephur@lemmy.world 4 points 1 year ago

    I create so many aliases with the notion of how much time I’ll save… never use ‘em. Works out okay though because a much richer history to fzf through

    [–] konakona@sh.itjust.works 4 points 1 year ago

    "python3 -m http.server"

    [–] titey@programming.dev 4 points 1 year ago

    This is the way!

    [–] Ignacio@kbin.social 3 points 1 year ago

    It's even faster if you look for it inside .bash_history.

    Yeah but last time I typed it, it worked. Who knows what ridiculous typos I'd make right now?

    [–] MavTheHack@lemmy.fmhy.ml 3 points 1 year ago

    I just use the 'fuck' command after lazily typing letters that somewhat match the command I want to run

    [–] watson387@sopuli.xyz 2 points 1 year ago

    Oh shit I definitely do this XD

    [–] pmarcilus@reddthat.com 2 points 1 year ago (2 children)

    Tfw I rather type it out instead of searching through the history

    load more comments (2 replies)
    [–] noduh@sh.itjust.works 2 points 1 year ago

    I just manage to forget what to type and I'm too lazy to look it up. that and I'm lazy

    [–] corytheboyd@kbin.social 2 points 1 year ago
    [–] vimdiesel@lemmy.world 2 points 1 year ago

    ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬆️ ⬇️ ⬇️

    [–] 737@lemmy.blahaj.zone 1 points 6 months ago

    i use vi mode in zsh for that reason, its pretty good

    [–] billygoat@lemmy.fmhy.ml 1 points 1 year ago

    I’ve always used set -o vi. Let’s you use vi commands on the bash prompt.

    load more comments
    view more: next ›