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

exit without saving history

Terminal - exit without saving history
kill -9 $$
2009-03-27 23:13:53
User: stu
Functions: kill
29
exit without saving history

this exits bash without saving the history. unlike explicitly disabling the history in some way, this works anywhere, and it works if you decide *after* issuing the command you don't want logged, that you don't want it logged

... $$ ( or ${$} ) is the pid of the current bash instance

this also works perfectly in shells that don't have $$ if you do something like

kill -9 `readlink /proc/self`

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Doesn't `readlink /proc/self` return the pid of the readlink program rather than the shell's pid?

Comment by bwoodacre 290 weeks and 4 days ago

heh, yeah, it does. So, time for me to stop assuming everything is a shell builtin :-)

Comment by stu 287 weeks and 4 days ago

I like this better, since a kitten dies every time you kill -9.

unset HISTFILE
Comment by syssyphus 283 weeks ago

This is not a good way to do things because you are ignoring anything else that might be done in .bash_logout.

A cleaner way to clear your running history is like this:

OLDHISTSIZE=$HISTSIZE

HISTSIZE=0

HISTSIZE=$OLDHISTSIZE

Also, don't count on being immune from logging by the system as some servers might be running exec loggers, which are independent of the shell.

Comment by deltaray 252 weeks and 2 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts