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.

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

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
16
Figure out what shell you're running

Alternatives

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
3

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

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

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
-3

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

/bin/zsh

/bin/bash

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

Comment by j_melis 186 weeks and 3 days ago

echo $0 is the best

Comment by RanyAlbeg 186 weeks and 3 days ago

Yes you're right. Thanks!

Comment by putnamhill 186 weeks and 1 day 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 186 weeks 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 185 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts