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.

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

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

Tags

Hide

Functions

grab all commandlinefu shell functions into a single file, suitable for sourcing.

Terminal - grab all commandlinefu shell functions into a single file, suitable for sourcing.
export QQ=$(mktemp -d);(cd $QQ; curl -s -O http://www.commandlinefu.com/commands/browse/sort-by-votes/plaintext/[0-2400:25];for i in $(perl -ne 'print "$1\n" if( /^(\w+\(\))/ )' *|sort -u);do grep -h -m1 -B1 $i *; done)|grep -v '^--' > clf.sh;rm -r $QQ
2010-01-30 19:47:42
User: bartonski
Functions: cd export grep mktemp perl sort
8
grab all commandlinefu shell functions into a single file, suitable for sourcing.

Each shell function has its own summary line, as a comment. If there are multiple shell functions with the same name, the function with the highest number of votes is put into the file.

Note: added 'grep -v' to the end of the pipeline, to eliminate extraneous lines containing only '--'. Thanks to matthewbauer for pointing this out.

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
curl -s http://www.commandlinefu.com/commands/browse/sort-by-votes/plaintext/[0-2400:25] | grep -oP "^\w+\(\)\ *{.*}"
2010-01-31 05:14:11
User: matthewbauer
Functions: grep
2

Much simpler but not as many features as the alternative.

Know a better way?

If you can do better, submit your command here.

What others think

Nice idea but it has all these "--" lines. If you delete those everything seems to be ok.

Comment by matthewbauer 105 weeks and 4 days ago

When I wrote the command, I didn't re-direct to a file... didn't notice the '--' lines.

Tried to add a grep -v to remove them, but pushed the command over 255 characters, so I'll have to golf it a little....

Comment by bartonski 105 weeks and 4 days ago

I've golfed the command and fixed the '--' problem... trouble is that I'm still getting several shell functions with the same name. The problem is that while 'grep -m1' should only include the first match on a given pattern, it seems that it's including the first match *per file*... I'll have to give this some thought.

Also, as an aside: there are a number of shell functions which have syntax errors... by far the most common is omitting the final ';' before the closing brace.

Comment by bartonski 105 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts