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

Extract raw URLs from a file

Terminal - Extract raw URLs from a file
egrep -ie "<*HREF=(.*?)>" index.html | awk -F\" '{print $2}' | grep ://
2009-02-05 17:51:14
User: wwest4
Functions: awk egrep grep
Extract raw URLs from a file


There are 2 alternatives - vote for the best!

Terminal - Alternatives
egrep -ie "<*HREF=(.*?)>" index.html | cut -d "\"" -f 2 | grep ://
2011-03-29 18:20:50
User: fanfani
Functions: cut egrep grep

you can also use cut instead of awk. less powerful but probably faster. ;)

Know a better way?

If you can do better, submit your command here.

What others think

This fails if the HREF attribute of the anchor tag used a single-quote instead of a double quote. It also fails if the HREF attribute isn't the first attribute of the tag, or if there are two spaces (or a newline) between the tag and the attribute, and so on. It also can be done much more efficiently with a single command e.g.

perl -ne 'print "$1\n" if m,+]href=["'\''](\w+://[^"'\'']+),i' index.html
Comment by Rhomboid 432 weeks and 6 days ago

sigh, and of course this crappy site mangled the command because it contained angle brackets.

Comment by Rhomboid 432 weeks and 6 days ago

ok, and i guess it would be easy enough to fix the regex to match the RFC, if necessary... aside from saying that efficiency doesn't really matter here, i can't really argue that perl is better suited to the task... you should post your soln if you can figure out how.

Comment by wwest4 432 weeks and 6 days ago

er... can't really argue AGAINST perl being better suited.

Comment by wwest4 432 weeks and 6 days ago

Your point of view

You must be signed in to comment.