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.

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:



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.

Top Tags



stderr in color

Terminal - stderr in color
mycommand 2> >(while read line; do echo -e "\e[01;31m$line\e[0m"; done)
2010-12-30 21:42:42
User: confiq
Functions: echo read
stderr in color

in case you run some command in CLI and would like to take read strerr little bit better, you can use the following command. It's also possible to grep it if necessary....


There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Can this be applied to the shell as well so that you set it once and it works for all subsequent commands?

Comment by stbu 225 weeks ago

This can be made into a function like so:

function red_error { "$@" 2> >(while read line; do echo -e "\e[01;31m$line\e[0m"; done) }

Then for example:

red_error tar tvf some_file.tgz
Comment by dstahlke 224 weeks and 1 day ago

Enter the function and the following into your .bashrc.

bind 'RETURN: "\e[1~error \e[4~\n"'

See http://superuser.com/questions/117227/a-command-before-every-bash-command for more info

Comment by capncanuck 224 weeks and 1 day ago

replace 'error' with the name of the function, in 'dstahlke''s case 'red_error'

Comment by capncanuck 224 weeks and 1 day ago

Hmm, it seems to interfere with 'read'

Comment by capncanuck 224 weeks and 1 day ago

It won't die when you hit Ctrl-C. You have to kill a bash process which is a child of the command being run...

Comment by dstahlke 223 weeks and 1 day ago

Another odd option:

exec 3> >(while read line; do echo -e "\e[01;31m$line\e[0m"; done) some_command 2>&3

stderr from some_command will be displayed in red. This opens file handle #3 and pipes it to the subshell until that file handle is closed with exec 3>&-

Comment by mweed 216 weeks ago

Note that doing:

exec 2> >(while read line; do echo -e "\e[01;31m$line\e[0m"; done)

Will make the shell do exectly what is wanted. all stderr displays in red and stdout displays normally for the shell and commands executed in the shell. Unfortunately is also has the effect of not displaying the prompt and any input until input is completed. Anyone know how to get around this?

Comment by mweed 216 weeks ago

Faster to color with command: grep --color=auto '.*'

Comment by mjb 179 weeks and 6 days ago

Your point of view

You must be signed in to comment.