all 16 comments

sorted by: hot top controversial new old
[–] 19 points 1 year ago (1 child)
  • [–] 17 points 1 year ago
    [–] 11 points 1 year ago

    It's either this or history | grep 'some-command'.

  • source
  • [–] 9 points 1 year ago

    You forgot a couple down arrows for when you overshoot.

  • source
  • [–] 9 points 1 year ago*

    history

    !982

  • source
  • [–] 7 points 1 year ago

    If you're in this picture try using fzf and backwards search, much more effective, hell even without fzf.

  • source
  • [–] 6 points 1 year ago
    [–] 4 points 1 year ago (1 child)
    [–] 4 points 1 year ago (2 children)

    Introducing: fish

    And then you just need to remember the first letters of the previously typed command

  • source
  • hideshow 2 child comments
  • [–] 4 points 1 year ago*

    The command you want is in the buffered history of a still running terminal that's doing something you don't want to close 💀

  • source
  • [–] 4 points 1 year ago

    Some of you haven't read the bash manual and it shows.

    Blow your mind to know about bang patterns. You've used !! but do you know about !$?

  • source
  • [–] 3 points 1 year ago

    If you haven't, try McFly - is a much better backwards / history search in the shell.

  • source
  • 144 comments in c/programmer_humor@programming.dev view that post