Hide

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.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

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:

Hide

News

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.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Get full directory path of a script regardless of where it is run from

Terminal - Get full directory path of a script regardless of where it is run from
BASEDIR=$(dirname $(readlink -f $0))
2011-12-01 09:10:21
User: mackaz
Functions: dirname readlink
3
Up
Down
Get full directory path of a script regardless of where it is run from

Also resolves symlinks, showing the full path of the link target

Add to favourites | Report as malicious

Alternatives

There are 5 alternatives - vote for the best!

Terminal - Alternatives
STARTING_DIR=$(cd $(dirname $0) && pwd)
2011-11-30 17:35:15
User: bbbco
Functions: cd dirname
Tags: cd dirname pwd variable
0
Up
Down
Get full directory path of a script regardless of where it is run from

Sometimes you need the full path to your script, regardless of how it was executed (which starting directory) in order to maintain other relative paths in the script.

If you attempt to just use something simple like:

STARTING_DIR="${0%/*}"

you will only get the relative path depending on where you first executed the script from.

You can get the relative path to the script (from your starting point) by using dirname, but you actually have to change directories and print the working directory to get the absolute full path.

Show sample output | Comments (2) | Add to favourites | Report as malicious
FULLPATH=$(perl -e "use Cwd 'abs_path';print abs_path('$0');")
2013-02-01 20:09:34
User: follier
Functions: perl
Tags: perl cd dirname pwd variable cwd abs_path
0
Up
Down
Get full directory path of a script regardless of where it is run from

Since none of the systems I work on have readlink, this works cross-platform (everywhere has perl, right?).

Note: This will resolve links.

Show sample output | Comments (0) | Add to favourites | Report as malicious
dirname $(readlink -f ${BASH_SOURCE[0]})
2011-12-02 16:10:38
User: unixyangg
Functions: dirname readlink
Tags: cd dirname pwd variable
-1
Up
Down
Get full directory path of a script regardless of where it is run from

work for execute file

Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

Your point of view

You must be signed in to comment.

Related sites and podcasts