• m15otw@feddit.uk
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 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)

  • tobier@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

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

    • amos@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 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@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    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.

  • vimdiesel@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

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

    • bastion@lemmy.fmhy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I use xonsh, which has decent history - start your command, and up arrow cycles through commands stating with what you typed.

      There’s good stuff and bad stuff about xonsh.

      • Parculis Marcilus@reddthat.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I rarely use fuzzy finder to search up the commands that I’m going to use. If you realise that a certain command with arguments is often being used, you should create an alias for it so that you don’t have need that memory load. That being said, I appreciate shell like fish provides auto complete (derived from command history) to speed up my workload.