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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags





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 2 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 290 weeks ago

what is the point of this command?

Comment by syssyphus 290 weeks 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 289 weeks and 6 days ago

Your point of view

You must be signed in to comment.