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:



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





Robust expansion (i.e. crash) of bash variables with a typo

Terminal - Robust expansion (i.e. crash) of bash variables with a typo
set -eu
2010-04-07 11:54:40
User: wipu
Functions: set
Robust expansion (i.e. crash) of bash variables with a typo

By default bash expands an unbound variable to an empty string. This can be dangerous, if a critical variable name (a path prefix for example) has a typo. The -u option causes bash to treat this as an error, and the -e option causes it to exit in case of an error. These two together will make your scripts a lot safer against typos.

The default behaviour can be explicitly requested using the ${NAME:-} syntax.

A (less explicit) variation: #!/bin/bash -eu


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

The -e and -u options are POSIX standard, so they should work with any /bin/sh, not just bash.

Comment by inof 287 weeks and 1 day ago

Btw, you need to be careful with commands like grep and find that exit with nonzero when they don't find anything. To make matters worse, failures like these are completely silent. These kinds of commands need to be "guarded" by e.g. adding '|| echo "Nothing found"' or something after them.

IMHO this kind of problem is less dangerous and easier to solve than the problems caused by not using set -eu, though.

Comment by wipu 209 weeks and 4 days ago

Your point of view

You must be signed in to comment.