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:
Run this in your music folder, or give the path directly after "find".
The sed pattern filters away the basename.
There are 3 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
locate .flac # hah! only 12 characters :-)
Ok, maybe adding "| less" would be helpful.
I honestly don't think there's anything wrong with this one, and I think people have gotten a bit too downvote-happy lately. Though I would suggest changing "uniq" to "sort -u". This is because while find often gives you some semblance of order to your results within directories, it's otherwise seemingly random. Therefore, this functionality of find you rely on may just be a convenient side effect and not a necessary property of the command.