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:



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





Figure out what shell you're running

Terminal - Figure out what shell you're running
echo $0
2011-02-05 16:42:48
User: chmurli
Functions: echo
Figure out what shell you're running


There is 1 alternative - vote for the best!

Terminal - Alternatives
readlink -f /proc/$$/exe
ps -p $$
2011-02-05 16:22:17
User: psykotron
Functions: ps

short, sweet, and works after sudoing a new shell.

ps -o comm= -p $$
2011-02-05 11:54:42
User: depesz
Functions: ps

First version was "ps uw -p $$", but current "ps -o comm= -p $$" just gives shell name

ps ho command $$
echo $SHELL
2011-02-05 11:06:40
User: lockie
Functions: echo

Isn't that simplier huh?

Know a better way?

If you can do better, submit your command here.

What others think

This doesn't work properly. Look at this snippet:

cat test.sh

readlink -f /proc/$$/exe

echo $SHELL

zsh test.sh



When running a script the $SHELL variable will not change, whereas the PID will, so it's more reliable.

Comment by j_melis 250 weeks and 4 days ago

echo $0 is the best

Comment by RanyAlbeg 250 weeks and 4 days ago

Yes you're right. Thanks!

Comment by putnamhill 250 weeks and 3 days ago
echo $0

returns the name of the current shell or program.

Pop it into a script and run it and it will return the name of the script not the name of the shell.

echo $SHELL is more reliable.
Comment by zlemini 250 weeks and 2 days ago

"echo $0" in guake returns "-" and in gnome-terminal returns "-bash".

If you run "exec -a csh bash", then in $0 you have "csh"

Comment by etam1024 250 weeks ago

Your point of view

You must be signed in to comment.