• HorreC
    link
    fedilink
    531 year ago

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

    • whofearsthenight
      link
      fedilink
      71 year ago

      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…

      • HorreC
        link
        fedilink
        31 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!

    • @fuckstick
      link
      English
      41 year ago

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

      • Bipta
        link
        fedilink
        3
        edit-2
        1 year ago

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

        • @fuckstick
          link
          English
          61 year ago

          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.

          • @gaiussabinus
            link
            English
            81 year ago

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

            • @fuckstick
              link
              English
              41 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

    • @DontRedditMyLemmy
      link
      31 year ago

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

      • @danielton
        link
        English
        10
        edit-2
        9 months ago

        deleted by creator

  • @[email protected]
    link
    fedilink
    English
    501 year ago

    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)

    • Skyler
      link
      fedilink
      71 year ago

      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

    • @[email protected]
      link
      fedilink
      English
      31 year ago

      didn’t know there was a comment for that, I just always used cat to read the bash history file

      • @[email protected]
        link
        fedilink
        English
        2
        edit-2
        1 year ago

        Wait until you learn about ctrl-R to search the bash history… :) If you press that and start typing, you will get auto complete from previous commands you typed. This is how an experienced linux user can be so fast in the terminal.

        There are even better tools for this, so ctrl R is just the built in way. Later you should look into https://github.com/junegunn/fzf

  • @vimdiesel
    link
    English
    101 year ago

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

  • @tobier
    link
    English
    91 year ago

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

    • @amos
      link
      English
      71 year ago

      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.

      • @[email protected]
        link
        fedilink
        English
        21 year ago

        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
          link
          English
          21 year ago

          That is default zsh history search, pretty nice.

          • @[email protected]
            link
            fedilink
            English
            11 year ago

            Oh is it just a setting then? I remember using plain zsh and it didn’t have that functionality until I installed omz, but I could see it being an option that omz enables on install.

            • @notavote
              link
              English
              11 year ago

              I think that it is.

    • @amos
      link
      English
      01 year ago

      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.

    • @amos
      link
      English
      01 year ago

      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.

  • @Aceticon
    link
    English
    81 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.

  • Ignacio
    link
    fedilink
    71 year ago

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

  • @[email protected]
    link
    fedilink
    English
    71 year ago

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

  • @Sketchpad01
    link
    English
    71 year ago

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

  • @Ephur
    link
    English
    51 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]
      link
      fedilink
      English
      4
      edit-2
      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.