Shell Command History

shameless plug: http://sysop.user.uucp.hu/bash-extended-history/content.md

i wonder why this isn't default bash history behavior? Wouldn't it be way more useful this way?

When dealing with bash history, I find that too many people are still unaware of C-r (Ctrl+R or Command+R): press it and start typing unique bits of your past commands. If multiple commands match, cycle through them with repeated C-r presses.The usual reaction is :mindblown: :)

In bash, you can type ^R, then text, to search that text in history interactively. Hit ^R again, if you want to see another match of same text. It saves lot of typing.

Wish history of previous commands and output were kept like a standard shell to scroll through and copy-paste things

Check out FZF for fuzzy finding through your command history in this manner- it is absolutely the superior way to search command history

> With Fish I never have to ask you again. I just remember part of it, and suddenly I've got it.Are you referring to something other than cycling through history?In bash, hit `Ctrl+R`, then type whatever part of the command to cycle through history.You may choose to adjust the size of the history file in `.bashrc` as needed.A good reference: <a href="https://www.digitalocean.com/community/tutorials/how-to-use-bash-history-commands-and-expansions-on-a-

I usually copy and paste my bash history to a LLM and ask questions. But I also use Ctrl (Cmd) + R for a exact keyword search.

Er, why not just use the `history` command (or hit the up arrow)?

What advantage does it have over zsh (or bash) native history?