The article feels incomplete for not not mentioning the bash built-in called bind. It allows you to work with the reeadline bindings.
I use Ctrl-R a lot to find previous commands from my shell history. Often I have to press Ctrl-R several or even many times to find the right one. And then it happens that I overshoot and would like to change the search direction. Unfortunately forward-search-history is on Ctrl-S, which is overloaded by flow control. Occasionally I use flow control, so I cannot remove that. What solution are others using to get forward-search-history?
If you’re open to a paradigm shift, I can’t recommend atuin highly enough. It’s truly the pinnacle of shell history tooling, but requires a ~1-2 day muscle-memory learning curve.
Comments
The article feels incomplete for not not mentioning the bash built-in called bind. It allows you to work with the reeadline bindings.
I use Ctrl-R a lot to find previous commands from my shell history. Often I have to press Ctrl-R several or even many times to find the right one. And then it happens that I overshoot and would like to change the search direction. Unfortunately forward-search-history is on Ctrl-S, which is overloaded by flow control. Occasionally I use flow control, so I cannot remove that. What solution are others using to get forward-search-history?
If you’re open to a paradigm shift, I can’t recommend atuin highly enough. It’s truly the pinnacle of shell history tooling, but requires a ~1-2 day muscle-memory learning curve.
https://atuin.sh/
fzf has pretty killer history fuzzy search. Just load its keybindings in your .bashrc