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/
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.
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
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:
Using avidemux to convert multiple files that are in the folder where the command was executed.
There are 3 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
A little more elegant:
for i in `ls`;do avidemux --video-codec Xvid4 --load $i --save ${i%%.*}-done.mp4 --quit; done
Or even more fail safe:
for i in `ls`;do avidemux --video-codec Xvid4 --load "${i}" --save "${i%%.*}"-done.mp4 --quit; doneJust I am just being silly.
thanks for the hints.
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
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
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