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.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

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

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

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)

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 164 weeks and 2 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 164 weeks and 2 days ago

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

Comment by sergeylukin 163 weeks and 5 days 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 163 weeks and 5 days ago

Your point of view

You must be signed in to comment.