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

Multiple variable assignments from command output in BASH

Terminal - Multiple variable assignments from command output in BASH
eval $(date +"day=%d; month=%m; year=%y")
2011-07-29 12:47:26
User: xakon
Functions: date eval
Multiple variable assignments from command output in BASH

It's quite easy to capture the output of a command and assign it in a shell's variable:

day=$(date +%d) month=$(date +%m)

But, what if we want to perform the same task with just one program invocation? Here comes the power of eval! date(1) outputs a string like "day=29; month=07; year=11" (notice the semicolons I added on purpose at date's custom output) which is a legal shell line. This like is then parsed and executed by the shell once again with the help of eval. Just setting 3 variables!

Inspired by LinuxJournal's column "Dave Taylor's Work the Shell".


There are 4 alternatives - vote for the best!

Terminal - Alternatives
read day month year <<< $(date +'%d %m %y')
2011-07-29 15:05:19
User: putnamhill
Functions: date read
Tags: bash read

This version uses read instead of eval.

read day month year < <(date +'%d %m %y')
2011-07-30 06:06:29
User: frans
Functions: date read
Tags: bash read

No command substitution but subshell redirection

Know a better way?

If you can do better, submit your command here.

What others think

Very nice!

Comment by flatcap 279 weeks and 4 days ago

Using 'eval' in any language makes me nervous. Still, even a curmudgeon like me can see how useful it is to treat instructions as data and vice-versa.

Comment by Mozai 279 weeks and 3 days ago

Not strangely, I have the same feelings about 'eval' in almost every language. Yet, I totally agree with you as I re-discover once again its power and the usefulness of going around the wall when it stands in front of you while trying to solve a problem!

And by the way, I should not forget the power of 'eval' in many Lisp-like languages!

Comment by xakon 279 weeks and 3 days ago

I like how eval works with the stat's -s option.

Comment by putnamhill 278 weeks and 6 days ago

How do you mean? Can you please provide an example of your point? stat(1) doesn't have a '-s' switch in my system!

Comment by xakon 278 weeks and 5 days ago

I see what you mean. I don't have that option on my linux systems either. Maybe it's just a BSD thing. This is how it works on my mac:

stat -s some.file

st_dev=234881026 st_ino=3657562 st_mode=0100644 st_nlink=1 st_uid=501 st_gid=20 st_rdev=0 st_size=478 st_atime=1312497217 st_mtime=1309535724 st_ctime=1309535724 st_birthtime=1309535658 st_blksize=4096 st_blocks=8 st_flags=0

When you eval the output of stat -s (if you have that option), you get a bunch of variables set.

Comment by putnamhill 278 weeks and 4 days ago

Your point of view

You must be signed in to comment.