list all executables in your path

ls `echo $PATH | sed 's/:/ /g'`
If run in bash, this will display all executables that are in your current $PATH
Sample Output
ls `echo $PATH | sed 's/:/ /g'`
/bin:
bash                      dmesg          mount           sh.distrib
bunzip2                   dnsdomainname  mountpoint      sleep
bzcat                     dumpkeys       mt              stty
bzcmp                     echo           mt-gnu          su
...
mii-diag                               vpddecode
mkboot                                 vpnc
mkinitramfs                            vpnc-connect
mkinitramfs-kpkg                       vpnc-disconnect
mklost+found                           vsftpd
mksmbpasswd                            winbindd
mysqld                                 xresprobe
mysqlmanager                           zic

4
By: archlich
2009-03-09 19:01:41

These Might Interest You

  • ##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 lpadmin time-admin network-admin svnadmin users-admin django-admin shares-admin services-admin


    5
    find ${PATH//:/ } -executable -type f -printf "%f\n"
    kamathln · 2009-02-16 06:03:46 1
  • I wanted to view only executables installed by a package. This seemed to work. There's got to be easier way, please share. Note: (1) Replace iptables with the package name of your interest (2) The command will trash any existing environment variable named 'lst' (3) Instead if you are interested in viewing just .ko or .so files installed by this package, then that would be easy: $ dpkg -L iptables | grep "\.[sk]o$" Show Sample Output


    1
    lst=`dpkg -L iptables` ; for f in $lst; do if [ -x $f ] && [ ! -d $f ] ; then echo $f; fi; done;
    b_t · 2010-10-30 14:47:45 1
  • Immediately after installing things into your PATH (e.g. under /usr/bin), currently open shells cannot find them ("zsh: command not found"). Use rehash to get the shell to rescan available executables.


    1
    rehash
    Pistos · 2009-03-02 19:03:07 2
  • Particularly useful on OS X where netstat doesn't have -p option. Show Sample Output


    18
    lsof -i -P | grep -i "listen"
    patko · 2010-10-14 09:37:51 3

What Others Think

Useful for a quick and dirty list.
jandro · 484 weeks ago
Interesting. I like it. If you don't care about where they are in your PATH, and don't need the list later, you could just use tab completion. <TAB> <TAB> It'll then ask if you want to "Display all ???? possibilites?" (About 6200, for me).
goodevilgenius · 484 weeks ago
Ugh. Backticks. ls $(echo $PATH | sed 's/:/ /g')
atoponce · 483 weeks and 6 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?

commandlinefu.com 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.

» 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: