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

Get absolut path to your bash-script

Terminal - Get absolut path to your bash-script
script_path=$(cd $(dirname $0);pwd)
2009-10-14 16:04:03
User: jgc
Functions: cd dirname
Get absolut path to your bash-script

Another way of doing it that's a bit clearer. I'm a fan of readable code.


There are 16 alternatives - vote for the best!

Terminal - Alternatives
PATH=$(cd ${0%/*}; pwd)

Know a better way?

If you can do better, submit your command here.

What others think


Comment by kaedenn 392 weeks and 6 days ago

what is the point of this command?

Comment by syssyphus 392 weeks and 6 days ago

Within a shell script you might need to work out where the script itself is located. For example if you had a script called myscript.sh and a config file called myscript.cfg in the same directory you might need to work out the full path to the config file. Using $(dirname $0) won't always give you the full path. It will provide the path that the script was executed with. This might be a relative path e.g. ../somedir/myscript.sh. The command would resolve that to /full/path/to/somedir/myscript.sh.

Hope my ramblings make sense.

Comment by jgc 392 weeks and 6 days ago

Your point of view

You must be signed in to comment.