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





SVN Add Recursively

Terminal - SVN Add Recursively
svn status | grep "^\?" | awk '{print $2}' | xargs svn add
2009-03-12 15:06:12
User: unixfu73000
Functions: awk grep xargs
SVN Add Recursively

This adds all new files to SVN recursively. It doesn't work for files that have spaces in their name, but why would you create a file with a space in its name in the first place?


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

The --include option to grep can make this less painful, in the event that you have temporary files lying around that change often and shouldn't be checked in. So if you only wanted to check in new C source files, use

grep --include="*.c" "^\?"

to only bring in new C files. Rinse and repeat with other file types.

Comment by bwoodacre 350 weeks and 1 day ago

Whoops. I just realized that my last comment was totally wrong. The --include option is when you're searching the content of files and you want to restrict which files are grepped.

Since I can't think of a way to do it with a single grep command at the moment, you could just tack on another grep pipe:

svn st | grep "^/?" | grep "\.m*$" | awk ...
Comment by bwoodacre 350 weeks and 1 day ago

You don't need the "" or the \? in your grep. You command could just be:

svn status | grep ^? | awk '{print $2}' | ls *.c | xargs svn add

Note you get aroudn the --include="*.c" this way...

Comment by Highwayman 350 weeks and 1 day ago

To merge the grep and awk pipes into one:

[code]svn st | awk '/^\?/{print $2}'[/code]

Comment by piXelz 330 weeks and 5 days ago

Your point of view

You must be signed in to comment.