gh or "grep history" - define a function gh combining history and grep to save typing

function gh () { history | grep $* ; } # gh or "grep history"
By defining a function "gh" as shown here, it saves me typing "history | grep" every time I need to search my shell history because now I only have to type "gh". A nifty time saver :-) You can also add the "gh" function definition to your .bashrc so it is defined each time you login. (updated 2015_01_29: changed from hg to gh to avoid clash with that other hg command. mnemonic: gh = grep history)
Sample Output
$ gh nut
 1661  sort -nut. -k 1,1 -k 2,2 -k 3,3 -k 4,4
 1737  # sort -nut. -k 1,1 -k 2,2 -k 3,3 -k 4,4
 1891  sort -nut. -k 1,1 -k 2,2 -k 3,3 -k 4,4 < IP_addresses > IP_addresses_sorted

By: mpb
2014-04-02 15:17:31

What Others Think

hg is the name of the mercurial cvs command, so I think it's not a good name choice for every body. also, you can make an alias for this like : alias hig="history|grep " # the space before the la double quote is important.
ayoli · 399 weeks and 5 days ago
I don't use the "mecurial cvs command" so it does not affect me. If you wanted to define a differently named function that's OK too. function moo () { history | grep $* ; } # define a function combining history and grep to save typing :-)
mpb · 399 weeks and 4 days ago
I just use Ctrl-r / Ctrl-s to search commands history in bash/zsh
sergeylukin · 399 weeks and 1 day ago
@sergeylukin Yes, I do ctrl-r. However, I also like to see a whole bunch of commands with a matching pattern to review and select which is what "hg" provides me with.
mpb · 399 weeks ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: