- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or # to comment.
CTRL+R
Or if you are not sure what it was at all: history
You forgot a couple down arrows for when you overshoot.
The command you want is in the buffered history of a still running terminal that’s doing something you don’t want to close 💀
Introducing:
fishAnd then you just need to remember the first letters of the previously typed command
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.
Look up
history-search-backwardin your favorite bash/readline manual.
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 !$?
Don’t call me out like that lol. Also Atuin is pretty cool for this as you are showed a list of the commands used when you press ⬆️.
Why would I type out this command that’s six whole keystrokes long when I can save time by pressing ‘up’ twenty times instead?
If you haven’t, try McFly - is a much better backwards / history search in the shell.
After a time ypu look into extending the history too… 500line by default is far too short for all the awesome commands
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
It’s either this or
history | grep 'some-command'.history!982Me with git pushes: up up up, enter x3. Like 6 times a day.
Just make some aliases and scripts you lunatic.
ctrl+r is your friend :)
With only three up presses, it would probably be faster than ctrl+r
Not me using Linux for 15 years and just learning you can search through previous commands…
I hope I’m not blowing your mind when I tell you that you can grep .bash_history?
Easy there wizard. In my defense I don’t hang out in a terminal all that much anymore.
lsIf you’re in this picture try using fzf and backwards search, much more effective, hell even without fzf.
