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

tee to a file descriptor

Terminal - tee to a file descriptor
tee >(cat - >&2)
2010-07-20 17:22:31
User: camocrazed
Functions: cat tee
tee to a file descriptor

the tee command does fine with file names, but not so much with file descriptors, such as &2 (stderr). This uses process redirection to tee to the specified descriptor.

In the sample output, it's being used to tee to stderr, which is connected with the terminal, and to wc -l, which is also outputting to the terminal. The result is the output of bash --version followed by the linecount


There are 3 alternatives - vote for the best!

Terminal - Alternatives
echo "tee can split a pipe in two"|tee >(rev) >(tr ' ' '_')
2010-08-14 20:38:59
User: axelabs
Functions: echo tee tr

Tee can be used to split a pipe into multiple streams for one or more process to work it. You can add more " >()" for even more fun.

Know a better way?

If you can do better, submit your command here.

What others think

This screams of a bash high-level usage of dup2(). I love it. This means I can "redirect" stdout to both stdout and stderr. But wouldn't

tee /dev/stderr

do the same thing, in a way that's a little more portable?

Comment by kaedenn 326 weeks and 6 days ago

Thanks kaedenn. I don't know wether it's more portable, but it is shorter and easier to read/memorize.

Comment by CodSpirit 326 weeks and 6 days ago

I think you're right there kaedenn, but then you're limited to the three regular ones that are duplicated in /dev, whereas the >(...) is resolved to a numerically named file in the /dev/fd directory, which gives you a few more options.

More reading here: http://www.gnu.org/software/bash/manual/bashref.html#Redirections

Also, if you want to do some further processing, you sort of need to use the process substitution method anyways. For example:

echo "foo" |tee >(sed 's/.*/& 2/' >&2)| sed 's/.*/& 1/'

should output a 2 next to the stderr copy, and a 1 next to the stdout copy. I'm not sure how you would do that using a write only file like /dev/stderr

Comment by camocrazed 325 weeks and 5 days ago

Your point of view

You must be signed in to comment.