Carly™ to [email protected]English • 1 year agoLook, I'm lazy, okay?lemmy.worldmessage-square85fedilinkarrow-up11.26K
arrow-up11.24KimageLook, I'm lazy, okay?lemmy.worldCarly™ to [email protected]English • 1 year agomessage-square85fedilink
minus-square@[email protected]linkfedilinkEnglish49•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]linkfedilinkEnglish8•1 year agoCtrl + S to go the other way if you overshoot!
minus-square@[email protected]linkfedilinkEnglish3•1 year agoCan’t just hit enter to run the one you want then, though.
minus-square@[email protected]linkfedilinkEnglish7•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.
But how to go backwards and forwards through the results? I just cycle through again!!
As @[email protected] said above, Ctrl+S
Wish I knew this sooner.