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 is a simple case of recursing through all directories, adding the '.bak' extension to every file. Of course, the 'cp $file $file.bak' could be any code you need to apply to your recursion, including tests, other functions, creating variables, doing math, etc. Simple and clean recursion.
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
When it comes to acting on all these files, find can do it directly :
find . -type f -exec cp {} {}.bak \;right, except when you want to execute multiple lines of code. then find gets ugly with all the -exec switches. then when introducing logic, it gets even worse. no, with this example, you're using find for the recursion, then a while loop to operate on files, so you can nest several commands easily.
You left out the quotation marks around your variable references -
this code as it is will break when filenames have spaces.
just for insanity's sake, *even with* the quotation marks, the code still breaks with filenames with newlines in them, but this does not:
USAGE: recfindexec
[code]
recfindexec() {
for dirs in "${1%/}"/*/; do [ -d "$dirs" ] && recfindexec "$dirs" "$2"; done
for files in "${1%/}"/$2; do [ -f "$files" ] && {
#YOUR CMDS IN HERE EX:
ls "$files"
} done
}
:P
^^USAGE: recfindexec search_dir wildcard
ex:
recfindexec Videos "*.avi"