In the terminal, I can type Ctrl + R to search for a matching command previously typed in BASH. E.g., if I type Ctrl + R then grep
, it lists my last grep
command, and I can hit enter to use it. This only gives one suggestion though. Is there any way to cycle through other previously typed matching commands?
4 Answers
If I understand the question correctly you should be able to cycle through alternatives by repeatedly hitting Ctrl + R.
E.g.:
- Ctrl + R
grep
- Ctrl + R
- Ctrl + R ...
That searches backwards through your history. To search forward instead, use Ctrl + S, but you may need to have set: stty -ixon
(either by .bash_profile
or manually) prior to that to disable the XON/XOFF feature which takes over Ctrl + S. If it happens anyway, use Ctrl + Q to re-enable screen output (More details here.)

- 1,025

- 28,811
If you feel the command will be used frequently, you could add a tag
command #useful
Then
Ctrl + R #useful
This works because #
is a comment delimiter, i.e. everything that comes after the symbol is not interpreted as a command. However, it will be recorded in the history and is thus searchable.
-
10
-
2
-
8@SudipBhandari just after your command. # starts a comment. E.g. ls -lah #useful – Andrei Dec 04 '16 at 09:27
-
38
-
6That's more a hack, and
.bash_history
gets flushed after a while. You'd be more comfortable using bash aliases – Nino Filiu Dec 11 '20 at 13:56 -
1Oh man. I was doing this by echoing whatever I wanted to remember, so I could search for the echo. This is better. – felwithe Mar 10 '21 at 19:39
-
-
The history file won't get flushed if you increase its line limit to int_max. I personally don't have any desire to truncate my shell history, it's never going to get big enough to be a problem. – forresthopkinsa Oct 24 '23 at 20:26
You can also set up the up and down arrows to do a slightly different search by adding these lines to ~/.inputrc:
"\e[A": history-search-backward
"\e[B": history-search-forward
Instead of searching for a substring anywhere in the command (like Ctrl-r) it will search for a command starting with the text to the left of the cursor. For example, if I run these commands:
$ ls bart
$ ls fools
then type ls
and press Up twice, it will show ls bart
and the cursor in the same place. Compare with Ctrl-r, where it would find the ls
twice in the last line, so you'd have to press it once again to find the previous line.
These approaches both have their strengths, and both of them can save a lot of time.
-
5This is also standard on OS X, so you don't need to create
~/.inputrc
and add those two lines. – DASKAjA Aug 12 '16 at 14:36 -
1As falconepi have written in the comments of this answer, on Ubuntu you just need to uncomment in
~/.inputrc
the two lines including history-search-* – Arpad Horvath Aug 16 '16 at 07:11 -
You could also look at this post for more details on this answer: http://codeinthehole.com/writing/the-most-important-command-line-tip-incremental-history-searching-with-inputrc/ – Andrei Dec 04 '16 at 09:48
-
2This wasn't standard on my macOS (10.13). I've always missed this functionality! – forthrin Mar 30 '18 at 11:02
-
1a good thing about this is that you can still use ctrl-p/ctrl-n for regular skimming through history – elig Sep 19 '18 at 02:46
There's a replacement for built-in Ctrl + R called hstr. It allows to search command history matching all search tokens at the same time (among other things), and cycle through result using arrow keys:
Here's is a demo screencast.
It can be installed on a Debian-family OS like:
add-apt-repository ppa:ultradvorka/ppa
apt-get update
apt-get install hstr
hstr --show-configuration >> ~/.bashrc
And then use Ctrl + R (after reopening the terminal).

- 2,438
CTRL+SHIFT+r
doesn't work for me. – Maxim Suslov Apr 05 '16 at 07:48[[ $- == *i* ]] && stty -ixon
to your .bashrc and thenCTRL+s
will work as the reverse ofCTRL+r
– gla3dr Apr 21 '16 at 17:03STRL+s
and it froze my terminal. Worth mentioning that you can unfreeze it withCTRL+q
as per https://unix.stackexchange.com/a/12108/265674 – user2740 Feb 05 '19 at 13:13stty -ixon
was the missing piece I've needed for 25 years to search forward. Can't believe it annoyed me for so long before I Googled it! :D – mhvelplund Feb 18 '21 at 07:09ctrl-R
first! if you typegrep ctrl-R
then it only shows the most recent command, and repeated presses ofctrl-R
do nothing. there's probably a really good reason for this, but i consider it a bug. – Spongman Sep 23 '21 at 16:57