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.

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



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Recursive replace of directory and file names in the current directory.

Terminal - Recursive replace of directory and file names in the current directory.
find . *oldname* | grep oldname | perl -p -e 's/^(.*)(oldname)(.*$)/mv $1$2$3 $1newname$3/' | sh
2009-07-26 01:22:24
User: pravus
Functions: find grep perl
Recursive replace of directory and file names in the current directory.

This should work anywhere perl and grep is available. :P


There is 1 alternative - vote for the best!

Terminal - Alternatives
for i in `find -name '*oldname*'`; do "mv $i ${i/oldname/newname/}"; done
2009-07-26 21:58:16
User: 0x89

no grep, no perl, no pipe.

even better in zsh/bash4:

for i in **/*oldname*; do "mv $i ${i/oldname/newname/}"; done

No find, no grep, no perl, no pipe

find -name '*oldname*' -print0 | xargs -0 rename 's/oldname/newname/'
2009-07-27 00:44:06
Functions: find rename xargs

This is better than doing a "for `find ...`; do ...; done", if any of the returned filenames have a space in them, it gets mangled. This should be able to handle any files.

Of course, this only works if you have rename installed on your system, so it's not a very portable command.

Know a better way?

If you can do better, submit your command here.

What others think

a) find . *oldname* will print every frickin file in the tree, and then print *oldname*: no such file or directory. Maybe you mean

find -name "*oldname*"

b) piping something to grep and then to one of the following is ALWAYS a waste:

sed, awk, perl.

You can get rid of grep and convert your perl to:

perl -n -e '/^(.*)(oldname)(.*$)/ && print "mv $& $1newname$3\n"'
Comment by 0x89 384 weeks ago

You are assuming

a) That that is unintentional. :P It is a lazy way of tracking what filenames were changed in case I made a mistake with oldname.

b) Ya, that part is better.

Comment by pravus 384 weeks ago

At least in the debian/ubuntu perl distribution there is a prename command (replacing util-linux rename) which would do this for you in one shot using find:

find . -name "*oldname*" -exec prename 's/oldname/newname/' {} +

If you are not quoting the *oldname* expression then find is matching only files&directories in the current directory because the shell is expanding *oldname* before find even gets called.

Comment by bwoodacre 383 weeks and 6 days ago

Your point of view

You must be signed in to comment.