I’m more of a tcsh user, where by default alt+p will search backwards for a command that starts with the text currently written in the prompt. So, type “vim” followed by alt+p as many times as necessary until I find the exact vim call that I’m looking for (normally followed by an alt+n because I pressed one too many times on p). In bash by default you have ctrl+r followed by the string you’re looking for and press ctrl+r until you find the command. I can see online that alt+p is bound by default to non-incremental-reverse-search-history, where I think history-search-backward would be a better match to tcsh’s behavior. Currently not at the computer so I can’t test it.
I’m more of a tcsh user, where by default alt+p will search backwards for a command that starts with the text currently written in the prompt. So, type “vim” followed by alt+p as many times as necessary until I find the exact vim call that I’m looking for (normally followed by an alt+n because I pressed one too many times on p). In bash by default you have ctrl+r followed by the string you’re looking for and press ctrl+r until you find the command. I can see online that alt+p is bound by default to non-incremental-reverse-search-history, where I think history-search-backward would be a better match to tcsh’s behavior. Currently not at the computer so I can’t test it.