What's this?

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/

Get involved!

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.

Universal configuration monitoring and system of record for IT.

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags



Get a list of commands for which there are no manpages

Terminal - 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
2010-07-26 19:39:53
User: camocrazed
Functions: file ls man
Get a list of commands for which there are no manpages

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 5 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

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
Comment by kaedenn 247 weeks and 4 days ago

This is a misuse of ls!

for file in /usr/bin/*; do ; done

is sufficient.

Comment by ScriptDevil 247 weeks and 3 days ago


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


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
Comment by camocrazed 247 weeks and 2 days ago

Your point of view

You must be signed in to comment.