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:
This command gives you the number of lines of every file in the folder and its subfolders matching the search options specified in the find command. It also gives the total amount of lines of these files.
The combination of print0 and files0-from options makes the whole command simple and efficient.
If you can do better, submit your command here.
You must be signed in to comment.
Less typing if you use the multi-argument -exec feature of find:
find . -name "*.sql" -exec wc -l {} +this will invoke wc once as well. Also bash 4.0 and zsh support the ** globbing string which I believe means "at any depth" so you could accomplish your goal in those shells with something like
wc -l **/*.sqlI'm not sure if you also have to include ./*.sql in addition to **/*.sql to get files in the cwd.
Didn't know about the ?-exec command {} +? multi argument option for find. That's a nice one, thanks :)