this post was submitted on 04 Jul 2023
1112 points (98.2% liked)

linuxmemes

21440 readers
799 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!


    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 fork-bomb your computer.

    founded 1 year ago
    MODERATORS
     
    top 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 50 points 1 year ago (6 children)

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

    [–] [email protected] 15 points 1 year ago (1 children)

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

    [–] [email protected] 6 points 1 year ago (1 children)

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

    [–] [email protected] 3 points 1 year ago

    Thanks for clearing up this mystery.

    [–] [email protected] 10 points 1 year ago (4 children)

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

    load more comments (4 replies)
    [–] [email protected] 7 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...

    [–] [email protected] 3 points 1 year ago

    you can hit it again after you are dialed in as much as you want and it will keep going back in time with the words you have in there and stuff that matches!

    [–] [email protected] 4 points 1 year ago (1 children)

    This. It took a while for it to sink in but now it’s muscle memory and a huge time saver

    [–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

    What now? What is r? How does this work?

    [–] [email protected] 5 points 1 year ago (1 children)

    CTRL+R brings up a prompt and allows you to search through commands you’ve run before. If you’ve run different variations of the command hitting CTRL+R or CTRL+SHIFT+R cycles through commands similar to what you’ve typed out.

    [–] [email protected] 6 points 1 year ago (1 children)

    I'm new to linux and i've been using $history | grep . This information is very useful, thank you.

    [–] [email protected] 3 points 1 year ago

    Sure thing! There’s lots of ways to do the same things, but either way stops you from hitting the up key a bajillion times

    [–] [email protected] 4 points 1 year ago

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

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

    Why r? Maybe if I knew why r, then I wouldn't forget this every 13 seconds...

    [–] [email protected] 9 points 1 year ago

    Reverse search

    [–] [email protected] 42 points 1 year ago (8 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 8 points 1 year ago (1 children)

    Use fzf for a more visual search.

    [–] [email protected] 3 points 1 year ago

    This is the way.

    [–] [email protected] 4 points 1 year ago (1 children)

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

    [–] [email protected] 5 points 1 year ago

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

    load more comments (6 replies)
    [–] [email protected] 9 points 1 year ago

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

    [–] [email protected] 9 points 1 year ago

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

    [–] [email protected] 8 points 1 year ago

    fzf masterrace

    [–] [email protected] 8 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.

    [–] [email protected] 6 points 1 year ago (4 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.

    load more comments (4 replies)
    load more comments (2 replies)
    [–] [email protected] 7 points 1 year ago (1 children)

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

    [–] [email protected] 2 points 1 year ago
    [–] [email protected] 6 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.

    [–] konakona 5 points 1 year ago

    "python3 -m http.server"

    [–] Socsa 5 points 1 year ago (1 children)

    We will history | grep docker until morale improves

    [–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

    Gah it's all docker container ps -a. OK, fine, history | grep "docker run".

    Next time I'll put a file in the project directory that tells me how I ran it and .gitignore it. I promise. Next time.

    [–] [email protected] 5 points 1 year ago

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

    [–] [email protected] 4 points 1 year ago
    [–] [email protected] 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

    [–] [email protected] 4 points 1 year ago

    history | grep {search term}

    [–] [email protected] 3 points 1 year ago
    [–] [email protected] 3 points 1 year ago

    This is the way!

    [–] [email protected] 3 points 1 year ago

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

    [–] [email protected] 2 points 1 year ago

    It's not about the keystrokes. It's the principle!

    [–] [email protected] 2 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 ›