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 example uses the -exec option to move all matching files into a backup directory
There are 3 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
Hmm... Be very careful when using find and mv like that. If you have duplicate filenames, bad things will happen. The first file gets moved to /tmp/backup, then then next file with that name will overwrite the first.
A safer idea would be to replace "mv" with "mv --backup=numbered". Now, each file will be given a unique name.
Should be replaced with something non-invasive for example, like ls instead of mv. Maybe this would be better:
find . -type f -exec ls -l {} \;
That executes ls on every file in the resulting list.
Both above are excellent ideas and points, also you may want to make this verbose as well as logging the output so that if something screws up, you have a record of it. sed and awk are your friends :)