The key here IMO is that you decide both when and how.
No such option with Windows, but if you like the GUI and are used to using that, I don’t see why anyone of their right mind would have a problem with that.
Personally I prefer to open a terminal and press the up key so I don’t have to type the command again, it takes 30 times until I get to the correct command, so it’s clearly slower, but hey we all have our little quirks.
Oh thanks for this. I’ve been using history | grep $something for the longest time, but i always end up copy pasting the actual command cause i didn’t remember how to invoke the number, and copy pasting is so quick that you end up never looking up how to do it properly lol.
The key here IMO is that you decide both when and how.
No such option with Windows, but if you like the GUI and are used to using that, I don’t see why anyone of their right mind would have a problem with that.
Personally I prefer to open a terminal and press the up key so I don’t have to type the command again, it takes 30 times until I get to the correct command, so it’s clearly slower, but hey we all have our little quirks.
history | grep <something I vaguely remember >
!<number of that command>
You can do reverse search but I’m too lazy to remember the sequence right now
I got a new function for my bash aliases file lol
Just use FZF (fuzzy search finder) with the CTRL+R keybind.
ctrl R then type
Never tried history | grep though. Thanks for the tip!
Oh thanks for this. I’ve been using
history | grep $somethingfor the longest time, but i always end up copy pasting the actual command cause i didn’t remember how to invoke the number, and copy pasting is so quick that you end up never looking up how to do it properly lol.