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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags





List all execs in $PATH, usefull for grepping the resulting list

Terminal - List all execs in $PATH, usefull for grepping the resulting list
find ${PATH//:/ } -executable -type f -printf "%f\n"
2009-02-16 06:03:46
User: kamathln
Functions: find
List all execs in $PATH, usefull for grepping the resulting list

##Dependancies: bash coreutils

Many executables in $PATH have the keyword somewhere other than the beginning in their file names. The command is useful for exploring the executables in $PATH like this.

find ${PATH//:/ } -executable -type f -printf "%f\n" |grep admin










There is 1 alternative - vote for the best!

Terminal - Alternatives
find ${PATH//:/ } -iname "*admin*" -executable -type f
2010-03-29 10:20:07
User: sanmiguel
Functions: find
Tags: bash find unix

While it seems (to me at least) a little counter-intuitive to filter on name first, this requires less work for find, as it allows it to immediately discount any files that do not match the name directly from the directory listing on disk. Querying against file attributes requires reading the file attributes, which is performed for all files matching any name based predicates.

Know a better way?

If you can do better, submit your command here.

What others think


If you would like to negate symlinks then use the -P option. Also, I recommend using -maxdepth 1 to prevent find from traversing into subdirectories. Shells do not traverse the subdirectories found in $PATH. For example, if PATH=/bin:/usr/local/bin and you have a subdirectory inside /usr/local/bin/xyz, the shell will NOT look in the xyz directory for your command thus the find command should do the same.


find -P ${PATH//:/ } -maxdepth 1 -executable -type f -printf "%f\n" | sort


Comment by greeneggs 170 weeks ago

Your point of view

You must be signed in to comment.