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

small one-line loop, change for different taste :P

Terminal - small one-line loop, change for different taste :P
for FILE in $(ls); do [COMMAND]; done
2009-02-17 14:42:46
User: stinger
small one-line loop, change for different taste :P

# Small for loop, that can list files in dir, and after that executes

# [COMMAND] of your choice, usefull for example rename, move, tar etc..

# change cmd's for different results :)


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 be easier (as written) or much more powerful. Yours, as written can be accomplished as...

for FILE in *;do echo $FILE;done

Also, can be made much more selective by doing something like...

for FILE in `ls | grep -v badstufff | awk '{print $2}'|`;do [command] $FILE;done

Comment by unixmonkey1114 431 weeks ago

unixmonkey1114: I actually like to do the $(ls) too, especially so I can ls in another directory.

For your second proposal, I tend to use "while" rather than "for", like :

ls | grep -v badstuff | awk '{print $2}' | while read line; do [command] $line; done

which I find clearer somehow.

Comment by raphink 431 weeks ago

Note: "while" and "for" are not equivalent in my last comment though. "for" takes spaces aswell as newlines as separator, whereas "while" only takes newlines, so it can be useful for multi-line values.

Comment by raphink 431 weeks ago

I often do:

for FILE in ...; do echo [COMMAND]; done

and then, if satisfied with the commands printed, I repeat the for command without echo

Comment by dz 431 weeks ago

Your point of view

You must be signed in to comment.