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 takes quite a while on my system. You may want to test it out with /bin first, or background it and keep working.
If you want to get rid of the "No manual entry for [whatever]" and just have the [whatever], use the following sed command after this one finishes.
sed -n 's/^No manual entry for \(.*\)/\1/p' nomanlist.txt
There are 7 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
No need for sed or even the text file.
for file in $(ls /usr/bin); do man -w $file 2>&1 | awk '/No/{print $5}'; doneThis is a misuse of ls!
for file in /usr/bin/*; do ; done
is sufficient.
@kaedenn
Looks good. You should submit it as an alternate command.
The reason for the extra file was so that I wasn't invoking sed several thousand times during the loop
@ScriptDevil
Have you even tried your way first? If I remove the ls command, I simply get a directory listing on stdout, not what I'm looking for.
If it works for you , great, but either post a full, working command so we see what you tried, or don't post one because it appears to me that you didn't even test your method before posting.
This is what I tried based on your post. I get stdout.txt full of the complete list of files, and stderr.txt is empty.
for file in /usr/bin/*; do man -w $file 2>>stderr.txt 1>>stdout.txt; done