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.

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

Extract all 7zip files in current directory taking filename spaces into account

Terminal - Extract all 7zip files in current directory taking filename spaces into account
savesIFS=$IFS;IFS=$(echo -en "\n\b"); for items in `ls *.7z`; do 7zr e $items ; done; IFS=$saveIFS
2010-01-22 14:16:09
User: BCK
Functions: echo
-7
Extract all 7zip files in current directory taking filename spaces into account

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
for file in *.7z; do 7zr e "$file"; done
find -maxdepth 1 -type f -name "*.7z" -exec 7zr e '{}' ';'
2010-01-23 19:50:10
User: minnmass
Functions: find
-1

Use find's built-in ability to call programs.

Alternatively,

find -maxdepth 1 -type f -name "*.7z" -print0 | xargx -0 -n 1 7zr e

would work, too.

7za x \*.zip

Know a better way?

If you can do better, submit your command here.

What others think

What a mess.

Comment by jmcantrell 234 weeks and 6 days ago

no, not a mess! This is a great example of what one can do to save IFS when necessary. While here it can be avoided, in other places this can be very handy, as set forth in the Advanced Bash Scripting Guide.

Comment by linuxrawkstar 234 weeks and 6 days ago

If you use find for this, then you don't have to worry about spaces or newlines in filenames:

find . -name "*.7z" -exec 7zr e {} \;

To strictly search only the current directory, put "-maxdepth 1" before -name. In BCK's defense, temporarily changing the IFS sometimes is the fastest way to do things instead of using many invocations of tr/sed/awk/cut/others.

Comment by bwoodacre 234 weeks and 6 days ago

another huge mess. why some people keep posting these lines without researching first? KISS!

for f in *.7z; do 7zr e "$f"; done

Comment by fsilveira 234 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts