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.

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

Recursive cat - concatenate files (filtered by extension) across multiple subdirectories into one file

Terminal - Recursive cat - concatenate files (filtered by extension) across multiple subdirectories into one file
find . -type f -name *.ext -exec cat {} > file.txt \;
2009-06-17 11:33:14
User: realgt
Functions: cat find
2
Recursive cat - concatenate files (filtered by extension) across multiple subdirectories into one file

Useful if you have to put together multiple files into one and they are scattered across subdirectories. For example: You need to combine all .sql files into one .sql file that would be sent to DBAs as a batch script.

You do get a warning if you create a file by the same extension as the ones your searching for.

find . -type f -name *.sql -exec cat {} > BatchFile.txt \;

Alternatives

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

You know you're rewriting the file on each output, right?

Comment by ubersoldat 253 weeks ago

@ubersoldat: No, he isn't. The output redirection is evaluated by the shell only once.

However, this can be done much easier, safer and more efficient with zsh (this is one of the many reasons why I love zsh):

cat **/*.ext > file.txt
Comment by inof 253 weeks ago

I think the argument to -name should be quoted, otherwise the shell is needlessly expanding it.

@inof I can see why one might think that you're cat-appending to the same file multiple times because the output redirection is put before the end of the argument to the -exec option. So a more readable and error-free form of the command would be:

find . -type f -name "*.ext" -exec cat {} \; >filename.txt

so that the arguments to find and the shell syntax are clearly separated. Bash 4.0 has added support for ** globbing, although this won't obsolete find :-).

Comment by bwoodacre 253 weeks ago

Good stuff guys, your comments assisted me to pull text out of binary files from multiple files and directories by essentially just replacing cat with strings. Thanks for sharing your knowledge.

find . -type f -name "*.*" -exec strings {} \; >alltext.out

Comment by gromburger 236 weeks ago

Hi guys! Can you please explain me the purpose of the final backslash just after file.txt?

Comment by clapclash 82 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts