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



runs a bash script in debugging mode

Terminal - runs a bash script in debugging mode
bash -x ./post_to_commandlinefu.sh
2009-02-25 19:10:21
User: nottings
Functions: bash
runs a bash script in debugging mode


There is 1 alternative - vote for the best!

Terminal - Alternatives
bash -x script.sh 2> log
bash -x SCRIPT
2009-03-13 00:09:07
User: jcalvert
Functions: bash

Display commands and their arguments as they are executed. Useful for debugging shell scripts.

bash -x test.sh 2>&1 | tee out.test
2009-09-03 17:10:44
User: arcege
Functions: bash tee

Sends both stdout and stderr to the pipe which captures the data in the file 'out.test' and sends to stdout of tee (likely /dev/tty unless redirected). Works on Bourne, Korn and Bash shells.

Know a better way?

If you can do better, submit your command here.

What others think

just running set -x first accomplishes the same thing

or, add set -x within your script at the point you want to turn debugging on

Comment by nottings 321 weeks and 5 days ago

Also debugging can be turned on at the top of the script when declaring the shell type: #!/bin/bash -x

Comment by hellspawn 321 weeks and 5 days ago

thanks hellspawn! didn't know that, but it makes sense.

Comment by nottings 321 weeks and 4 days ago

Thanks chaps. Made a lot of people at my place very happy.

Comment by mccalni 319 weeks and 4 days ago

How is it debugging? Does is it just more verbose?

It would be cool if there was a "safe-mode" where it blocks all writes to devices.

Comment by matthewbauer 290 weeks and 5 days ago



for tips for safer, more robust coding

Comment by nottings 231 weeks and 5 days ago

Inside script "set -x" turns on debugging. "set +x" turns off debugging. Bash example:

set -x; ls; ps; set +x
Comment by 0xFF 104 weeks and 2 days ago

Your point of view

You must be signed in to comment.