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

Rename .JPG to .jpg recursively

Terminal - Rename .JPG to .jpg recursively
find /path/to/images -name '*.JPG' -exec bash -c 'mv "$1" "${1/%.JPG/.jpg}"' -- {} \;
2010-01-07 15:41:17
User: sorpigal
Functions: bash find
7
Up
Down
Rename .JPG to .jpg recursively

Recursively rename .JPG to .jpg using standard find and mv. It's generally better to use a standard tool if doing so is not much more difficult.

Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
find /path/to/images -name '*.JPG' -exec rename "s/.JPG/.jpg/g" \{\} \;
2010-01-02 19:12:37
User: renich
Functions: find rename
Tags: find rename
8
Up
Down
Rename .JPG to .jpg recursively

This command is useful for renaming a clipart, pic gallery or your photo collection. It will only change the big caps to small ones (on the extension).

Show sample output | Comments (5) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

find /path/to/images -name '*.jpg' -exec rename.ul .JPG .jpg {} +

rename.ul is the util-linux rename command, widely available on linux systems, possibly named just 'rename' if not overridden by perl rename (prename). Also here I use the + form of -exec instead of \; so that find will launch rename.ul on many file names at once, using many fewer process spawns. With -exec bash -c mv ... you launch a shell process which launches a mv process just to rename one file. It works, but for performance, you'd be much better off writing a shell script, which is a very standard tool.

Comment by bwoodacre 175 weeks and 3 days ago

Thanks sorpigal.

This did exactly what I needed it to. I tried the other command but it failed. Maybe I had a typo.

@ bwoodacre. I should have totally used + instead of \; Dooh!

Comment by Xinerama 132 weeks ago

Using the "-exec" option of "find" is not a good technique. Basically while it is running a command "find" is waiting, and not 'searching' for the next file.

This is why piping the output of "find" into "xargs" is a better idea. The filename gets cached by the pipeline ready for "xargs" to use when ready, while "find" continues to search.

See find -exec vs xargs

http://www.sunmanagers.org/pipermail/summaries/2005-March/006255.html

Also look at commands like "mv_perl" whcih can rename multiple files in the one command. You can have "xargs" feed lots of files to each command, or just one one command per directory.

Comment by anthony 132 weeks ago

Your point of view

You must be signed in to comment.

Related sites and podcasts