Carly™ to linuxmemesEnglish • 1 year agoLook, I'm lazy, okay?imagemessage-square85arrow-up11.27Karrow-down118
arrow-up11.26Karrow-down1imageLook, I'm lazy, okay?Carly™ to linuxmemesEnglish • 1 year agomessage-square85
minus-square@[email protected]linkfedilinkEnglish50•1 year agoCtrl+R Then type any part of the command (filename, search string, etc) Ctrl+R again to cycle through the matches. (Best feature in bash)
minus-square@[email protected]linkfedilinkEnglish8•1 year agoI’ve been using this for a long time, never knew I could press Ctrl + R again. Thanks!
minus-square@[email protected]linkfedilinkEnglish3•1 year agoCan’t just hit enter to run the one you want then, though.
minus-square@rufuslinkEnglish7•1 year agoType: !1234 … to run whatever history number of the command.
minus-square@[email protected]linkfedilinkEnglish1•1 year agoBut how to go backwards and forwards through the results? I just cycle through again!!
minus-square@[email protected]linkfedilinkEnglish1•1 year agoAs @[email protected] said above, Ctrl+S
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)
Use fzf for a more visual search.
This is the way.
I’ve been using this for a long time, never knew I could press Ctrl + R again. Thanks!
Ctrl + S to go the other way if you overshoot!
Or
history | grep 'command'Can’t just hit enter to run the one you want then, though.
Type: !1234 … to run whatever history number of the command.
Wish I knew this sooner.
But how to go backwards and forwards through the results? I just cycle through again!!
As @[email protected] said above, Ctrl+S