How to cycle through reverse-i-search in Bash?

Question

In the GNU bash shell, I can type Ctrl + R to search for a matching command previously run. E.g., if I type Ctrl + R and 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?

score 1172 · Accepted Answer · edited Feb 14 '23 at 10:13

1172

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.)

edited Feb 14 '23 at 10:13

Peter Mortensen

1,016

answered Apr 24 '13 at 02:31

Runium

30,319

20

And use Ctrl+Shift+r for reverse scrolling if you happen to pass over. – wiswit Nov 01 '15 at 13:41
65

@wiswit CTRL+SHIFT+r doesn't work for me. – Maxim Suslov Apr 05 '16 at 07:48
19

@MaximSuslov See this question: http://stackoverflow.com/questions/791765/unable-to-forward-search-bash-history-similarly-as-with-ctrl-r/791800#791800 You can add [[ $- == *i* ]] && stty -ixon to your .bashrc and then CTRL+s will work as the reverse of CTRL+r – gla3dr Apr 21 '16 at 17:03
5

I just tried STRL+s and it froze my terminal. Worth mentioning that you can unfreeze it with CTRL+q as per https://unix.stackexchange.com/a/12108/265674 – user2740 Feb 05 '19 at 13:13
2

btw: you have to type the ctrl-R first! if you type grep ctrl-R then it only shows the most recent command, and repeated presses of ctrl-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

score 383 · Answer 2 · edited Mar 08 '21 at 16:22

383

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.

edited Mar 08 '21 at 16:22

Neuron

121

answered Nov 09 '14 at 08:07

Sathyam

3,968

12

Usually I do like this kind of tagging. #trg_bld #open_log – Makesh Jul 31 '15 at 05:50
2

where to add this tag? – Sudip Bhandari Nov 03 '16 at 13:46
9

@SudipBhandari just after your command. # starts a comment. E.g. ls -lah #useful – Andrei Dec 04 '16 at 09:27
50

Unix had hashtags before it was cool :))) – Jencel Oct 11 '19 at 11:44
9

That'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
2

Oh 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
good # better $ history fzf --query "''good" – Cymatical Oct 04 '21 at 23:42
1

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

score 80 · Answer 3 · edited Apr 13 '17 at 12:36

80

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.

edited Apr 13 '17 at 12:36

Community

1

answered Apr 24 '13 at 09:20

l0b0

53,976

5

This 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
1

As 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
3

This wasn't standard on my macOS (10.13). I've always missed this functionality! – forthrin Mar 30 '18 at 11:02
1

a 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

score 36 · Answer 4 · answered Aug 01 '19 at 19:37

36

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:

Example

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).

answered Aug 01 '19 at 19:37

saaj

2,636
1
16
8

1

This MUST be the accepted answer in my view. Thank you! – Nam G VU Oct 27 '20 at 00:13
Awesome, working!!! – infiniteLearner Mar 01 '22 at 12:14
3

Newer and a bit fancier: https://github.com/ellie/atuin – Caleb Feb 13 '23 at 22:27

How to cycle through reverse-i-search in Bash?

4 Answers4

Linked