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.

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



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Returns the absolute path to a command, using which if needed

Terminal - Returns the absolute path to a command, using which if needed
get_absolute_path() { echo $1 | sed "s|^\([^/].*/.*\)|$(pwd)/\1|;s|^\([^/]*\)$|$(which -- $1)|;s|^$|$1|"; }
2011-09-13 11:06:55
User: keymon
Functions: echo sed
Returns the absolute path to a command, using which if needed

It will return the absolute location of the called a script. If is in $PATH, it will search it using which.

You can combine this function with this other one: http://www.commandlinefu.com/commands/view/9252/readlink-equivalent-using-shell-commands-and-following-all-links, to get a way to know where is the real location of a called script:

# Returns the realpath of a called command. whereis_realpath() { local SCRIPT_PATH=$(whereis $1); myreadlink ${SCRIPT_PATH} | sed "s|^\([^/].*\)\$|$(dirname ${SCRIPT_PATH})/\1|"; }


There is 1 alternative - vote for the best!

Terminal - Alternatives
which any_path/a_command.sh | sed "s|^./|$(pwd)|"
2011-09-22 10:38:56
User: keymon
Functions: sed which

This works in multiple unixes, not only linux, for different paths.

On solaris, if you do not have which, you can use:

ksh whence -p anypath/a_command.sh | sed "s|^./|$(pwd)|" ksh whence -p

Know a better way?

If you can do better, submit your command here.

What others think

I don't get the reason for this... "which" does the exact same here:

ahu:~$ which ls


or the type command:

ahu:~$ type ls

ls is /bin/ls

Comment by peshay 297 weeks and 1 day ago

`whereis' is already a command:

whereis ls ls: /bin/ls /usr/bin/ls /usr/X11R6/bin/ls /usr/bin/X11/ls /usr/X11/bin/ls /usr/man/man1/ls.1.gz /usr/share/man/man1/ls.1.gz /usr/X11/man/man1/ls.1.gz
Comment by h3xx 297 weeks ago

I changed the function name.

which does the same?

$ touch a_command.sh ; chmod +x a_command.sh

$ which a_command.sh


$ type a_command.sh

a_command.sh is ./a_command.sh

I am not getting the absolute path here.

But you are right that you can do:

which a_command.sh | sed "s|^./|$(pwd)|"

Comment by keymon 296 weeks ago

Your point of view

You must be signed in to comment.