Get a list of commands for which there are no manpages

for file in $(ls /usr/bin ) ; do man -w $file 2>> nomanlist.txt >/dev/null ; done
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
Sample Output
No manual entry for kwsdl_compiler
No manual entry for kxforms
No manual entry for kxkb
No manual entry for kxml_compiler
No manual entry for kxsconfig
No manual entry for kxsrun
No manual entry for
No manual entry for lavaddwav
No manual entry for lavinfo
No manual entry for

2010-07-26 19:39:53

What Others Think

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}'; done
kaedenn · 617 weeks ago
This is a misuse of ls! for file in /usr/bin/*; do ; done is sufficient.
ScriptDevil · 616 weeks and 5 days ago
@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
camocrazed · 616 weeks and 5 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands

Stay in the loop…

Follow the Tweets.

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.


Subscribe to the feeds.

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: