Searches $PATH for files using grep

IFS=:; find $PATH | grep pattern
Best to put it in a file somewhere in your path. (I call the file spath) #!/bin/bash IFS=:; find $PATH | grep $1 Usage: $ spath php
Sample Output
$ IFS=:; find $PATH | grep php

By: camspiers
2009-08-14 13:38:58

What Others Think

A bit shorter version wrapped in function (which is must-do, otherwise you can't use $1): function path-grep() { dirs=${PATH//:/\ } find $(echo $dirs) | egrep $1 }
botanicus · 569 weeks and 2 days ago
Yes as I mentioned in the description you can put it in a file. Which on my machine, ubuntu 9.04 allows you to obtain the users input via $1. I like how you don't use a for loop. Nice!
camspiers · 569 weeks and 2 days ago
find will recurse. Although it is unusual for a PATH dir to have subdirs, the fact is you may get false matches if they do, and one of the dubdirs has a file matching the name you're looking for. And really, what is wrong with: which cat /bin/cat
sitaram · 569 weeks and 2 days ago
I just find it useful when given a server I don't know. Allows my to quickly determine what mysql tools are installed for example. "which" doesn't really help if you want partial matches.
camspiers · 569 weeks and 2 days ago
aah... partial matches. OK: ( IFS=:; find $PATH | grep pattern ) wrap it in a function and use $1 if you like :)
sitaram · 569 weeks and 1 day ago
For just a listing you could also do: IFS=: find $PATH -type f the change to IFS when at the beginning of the line goes only applies for that single command (at least in bash). You see a lot of this in Gentoo Linux. Neat idea.
bwoodacre · 569 weeks and 1 day ago
sitaram: That is awesome! I didn't know about the IFS. I have changed the command to specific : as the custom IFS.
camspiers · 569 weeks 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: