Hide

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.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

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:

Hide

News

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.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Perform a branching conditional

Terminal - Perform a branching conditional
true && { echo success;} || { echo failed; }
2009-04-02 01:49:25
User: clockworkavian
Functions: echo true
23
Up
Down
Perform a branching conditional

This will perform one of two blocks of code, depending on the condition of the first. Essentially is a bash terniary operator.

To tell if a machine is up:

ping -c1 machine { echo succes;} || { echo failed; }

Because of the bash { } block operators, you can have multiple commands

ping -c1 machine && { echo success;log-timestamp.sh }|| { echo failed; email-admin.sh; }

Tips:

Remember, the { } operators are treated by bash as a reserved word: as such, they need a space on either side.

If you have a command that can fail at the end of the true block, consider ending said block with 'false' to prevent accidental execution

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 9 alternatives - vote for the best!

Terminal - Alternatives
[[ test_condition ]] && if_true_do_this || otherwise_do_that
2009-02-20 21:45:21
User: stallmer
23
Up
Down
Instead of writing a multiline if/then/else/fi construct you can do that by one line

instead of writing:

if [[ "$1" == "$2" ]]; then

echo "$1 is equal $2"

else

echo "$1 differs from $2"

fi

do write:

[[ "$1" == "$2" ]] && echo "$1 is equal $2" || echo "$1 differs from $2"

Comments (2) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

and what about this case?

true && { false; } || { echo failed; }

try it :D

Comment by acirulli 219 weeks and 5 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts