Hide

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

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:

Hide

News

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!
Hide

Top Tags

Hide

Functions

Hide

Credits

Google verbatim search on your terminal

Terminal - Google verbatim search on your terminal
function google { Q="$@"; GOOG_URL='https://www.google.de/search?tbs=li:1&q='; AGENT="Mozilla/4.0"; stream=$(curl -A "$AGENT" -skLm 10 "${GOOG_URL}${Q//\ /+}" | grep -oP '\/url\?q=.+?&amp' | sed 's|/url?q=||; s|&amp||'); echo -e "${stream//\%/\x}"; }
2013-04-05 08:04:15
User: michelsberg
Functions: echo grep sed
13
Google verbatim search on your terminal

Put it in your ~/.bashrc

usage:

google word1 word2 word3...

google '"this search gets quoted"'

Alternatives

There are 3 alternatives - vote for the best!

Terminal - Alternatives
Q="YOURSEARCH"; GOOG_URL="http://www.google.com/search?q="; AGENT="Mozilla/4.0"; stream=$(curl -A "$AGENT" -skLm 10 "${GOOG_URL}\"${Q/\ /+}\"" | grep -oP '\/url\?q=.+?&amp' | sed 's/\/url?q=//;s/&amp//'); echo -e "${stream//\%/\x}"
2013-04-03 09:56:41
User: techie
Functions: echo grep sed
Tags: google
9

I found this command on a different site and thought you guy might enjoy it. Just change "YOURSEARCH" to what ever you want to search. Example, "Linux Commands"

Know a better way?

If you can do better, submit your command here.

What others think

This doesn't work on Mountain Lion because the Perl regex option was removed from grep. See http://www.dirtdon.com/?p=1452 for solutions

Comment by unixmonkey52593 111 weeks ago

@unixmonkey52593

I just descended deeper into RegEx hell than can be healthy, but found no working replacement for grep -P. :-(

The problem is as follows. Google returns something like this:

/url?q=http://www.example.com/fooWith;anyURLchar.html&bar&foo&baz&amp

The grep command with perl-regex outputs this:

/url?q=http://www.example.com/fooWith;anyURLchar.html&amp

Using grep's extended regex, I am only able to match the entire line again:

/url?q=http://www.example.com/fooWith;anyURLchar.html&bar&foo&baz&amp

I don't understand why the perl regex magically stops after the first "&" and how to get that working with a more portable tool.

Does anybody have an idea for that?

Comment by michelsberg 111 weeks ago

Try

egrep '/url\?q=[^&]+&amp'

or just with sed (grep isn't actually needed here):

sed '/.*\/url?q=\([^&]*\)&amp.*/\1/'
Comment by unixmonkey52650 111 weeks ago

Your point of view

You must be signed in to comment.