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.

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.

Know a better way?

What others think

I've been using a similar compound command for some time, but this approach has the same problem as mine: it invokes du twice, which can be slow in some cases. The only way that I can think of to get around this problem is to get the du totals in the normal numeric form, and then have the command translate the numbers into human-readable form. That seems a shame, since the code to generate human-readable output already exists in du. Maybe the best solution is to submit a patch to give the du command a new switch: sort the output by total size.