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:
If a directory name contains space xargs will do the wrong thing. Parallel https://savannah.nongnu.org/projects/parallel/ deals better with that.
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
That is, xargs does the "wrong thing" by default, but you can tell it to use any delimiter to separate arguments with the --delimeter option, such as a newline. xargs can also launch jobs in parallel with the -P option. It's good to know about the parallel command though, it's a perl script; I can't find it in Debian/Ubuntu though.
xargs has several race conditions if you use -P:
xargs will not guarantee you output with the biggest directory first. It will instead first output the job that finishes first. This is likely to be a problem here.
xargs may mix output, so output lines of jobs printing simultaneously can be mixed. This is not likely to be a problem here.
The solution using parallel prevents these two problems.
@bwoodacre: I have tried to think a way to fixup the xargs solution for the following dir. Can you fix it up?
mkdir '12" records'