What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags



define a function

Terminal - define a function
function gh () { history | grep $* ; } # define a function combining history and grep to save typing :-)
2014-04-02 15:17:31
User: mpb
Functions: grep
define a function

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)


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

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.

Comment by ayoli 55 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 :-)

Comment by mpb 55 weeks and 5 days ago

I just use Ctrl-r / Ctrl-s to search commands history in bash/zsh

Comment by sergeylukin 55 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.

Comment by mpb 55 weeks and 1 day ago

Your point of view

You must be signed in to comment.