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.

Universal configuration monitoring and system of record for IT.
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

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

Top Tags

Hide

Functions

Hide

Credits

Execute a command without saving it in the history

Terminal - Execute a command without saving it in the history
HISTFILE= ; your_secret_command
2012-01-26 21:08:57
User: titan2x
0
Execute a command without saving it in the history

Yes, by correctly setting the HIST* variables you can make certain commands not saved in history. But that's complicated and easy to make a mistake. If you set HISTFILE= to blank, nothing in your current shell session will be saved in history. Although this is not a precise answer to the subject, but it's very simple.

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives
<space>command
2009-03-17 16:25:29
User: eaZy
388

Prepending one or more spaces to your command won't be saved in history.

Useful for pr0n or passwords on the commandline.

Tested on BASH.

cat | bash
2010-08-18 13:47:46
User: glaudiston
Functions: cat
6

Sometimes you don't want to leave history, because of passwords use or somethink like.

I think it help.

read -e -s -p "Password: " password
2010-08-18 17:53:27
User: freiheit
Functions: read
3
wget --user=username --password="$password" http://example.org/

Instead of hiding commands entirely from history, I prefer to use "read" to put the password into a variable, and then use that variable in the commands instead of the password. Without the "-e" and "-s" it should work in any bourne-type shell, but the -s is what makes sure the password doesn't get echoed to the screen at all. (-e makes editing work a bit better)

export HISTCONTROL=ignorespace
2013-07-25 08:31:10
User: gorynka
Functions: export
2
<space>secret_command;export HISTCONTROL=

This will make "secret_command" not appear in "history" list.

<space> secret -p password
2011-09-16 12:41:16
User: pcholt
0

Put a space in front of your command on the command line and it will not be logged as part of your command line history.

Know a better way?

If you can do better, submit your command here.

Your point of view

You must be signed in to comment.