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

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
-4
Up
Down
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 :)

Add to favourites | Report as malicious

Alternatives

There are 8 alternatives - 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 221 weeks and 5 days 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 221 weeks and 5 days 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 221 weeks and 5 days 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 221 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts