• beerclue@lemmy.world
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    14 days ago

    i for one can’t be bothered to remember, for example, the syntax to add a new gitlab project to the allowed list of a hashicorp vault policy :) - i use zsh with fzf and ag, so i ctrl+r to find the last time i used this, adjust, execute.

    there are many use cases for checking out your shell’s command history…

      • hallettj@leminal.space
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        14 days ago
        • It has a nice interface for searching history - nicer than the history search included with the shells I’ve used
        • It has a “workspace” mode - it remembers which directory commands were run in, which gives you the option to limit history search to commands run in the same directory, which are often most relevant to the project you’re working on in that directory
        • If you want you can back up, or sync history to multiple machines. I know I’ve been in situations where I know the command I want is in history, but it’s in history on my desktop, and I’m on my laptop at the moment
      • Jade@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        13 days ago

        Bash by default limits history to ~1000 items iirc, and doesn’t store anything but the command itself