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.

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



Convert multiple files using avidemux

Terminal - Convert multiple files using avidemux
for i in `ls`;do avidemux --video-codec Xvid4 --load $i --save $i.mp4 --quit; done
2009-09-10 01:38:42
User: gean01
Convert multiple files using avidemux

Using avidemux to convert multiple files that are in the folder where the command was executed.


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

A little more elegant:

for i in `ls`;do avidemux --video-codec Xvid4 --load $i --save ${i%%.*}-done.mp4 --quit; done

Comment by DaveQB 359 weeks and 2 days ago

Or even more fail safe:

for i in `ls`;do avidemux --video-codec Xvid4 --load "${i}" --save "${i%%.*}"-done.mp4 --quit; done

Just I am just being silly.

Comment by DaveQB 359 weeks and 2 days ago

thanks for the hints.

Comment by gean01 359 weeks and 2 days ago

I think it's better to allow bash to do it's own expansion, instead of using the command substituted `ls`, which can return errors with color codes in some versions of bash. better is:

for i in * ; do ...

check out http://mywiki.wooledge.org/BashPitfalls#for_i_in_.60ls_.2A.mp3.60

Comment by thebillywayne 359 weeks and 2 days ago

you still run into problems with all of the above suggestions when the filenames contain any whitespace. :( serious bash PITA. usually the only way to get around it is to use the find/xargs null bit terminator trick

Comment by linuxrawkstar 359 weeks and 1 day ago

in bash if you wrap variable in double quotes you can fix the whole whitespace issue... ie-

for video in *avi;do avidemux --video-codec Xvid4 --load "$video" --save "$video".mp4 --quit; done

Comment by splaer 301 weeks and 3 days ago

Your point of view

You must be signed in to comment.