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/
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.
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
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:
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
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
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}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!
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
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.
aah... partial matches. OK:
( IFS=:; find $PATH | grep pattern )wrap it in a function and use $1 if you like :)
For just a listing you could also do:
IFS=: find $PATH -type fthe 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.
sitaram: That is awesome! I didn't know about the IFS. I have changed the command to specific : as the custom IFS.