- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
You must log in or # to comment.
Ctrl-r was right there.
Or sometimes
historyif I can’t remember at all.Oh my bad, two other people said that too I was just excited
CTRL+R
It’s either this or
history | grep 'some-command'.You forgot a couple down arrows for when you overshoot.
history!982If you’re in this picture try using fzf and backwards search, much more effective, hell even without fzf.
lsIntroducing:
fishAnd then you just need to remember the first letters of the previously typed command
Look up
history-search-backwardin your favorite bash/readline manual.Yup, I started using fish a while back and autocomplete is what kept me on it. The best part is that it’s contextual based on the folder you’re in.
🐟🐟🐟
🚫
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 !$?
The command you want is in the buffered history of a still running terminal that’s doing something you don’t want to close 💀
If you haven’t, try McFly - is a much better backwards / history search in the shell.
