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

Write on the console without being registered

Terminal - Write on the console without being registered
history -d $((HISTCMD-1)) && command_to_run

Alternatives

There are 5 alternatives - vote for the best!

Terminal - Alternatives
_ls
2013-02-02 00:44:01
User: marcusEting
Tags: history
4

just use a space to prevent commands from being recorded in bash's history on most systems

Know a better way?

If you can do better, submit your command here.

What others think

This can be done also by preceding the command with a whitespace.

pwd # is logged to history pwd # is not logged
Comment by reeloo 120 weeks and 4 days ago

This can be done also by preceding the command with an extra whitespace.

$ pwd # is logged to history $ pwd # is not logged
Comment by reeloo 120 weeks and 4 days ago

This can be done also by preceding the command with a whitespace. ;)

Comment by reeloo 120 weeks and 4 days ago

This can be done also by preceding the command with an extra whitespace.

Comment by reeloo 120 weeks and 4 days ago

preceding the command with a whitespace didn't work on centos 5/6

Comment by bunam 120 weeks and 4 days ago

IF you're using bash AND you have either 'ignorespace' in $HISTCONTROL, or $HISTIGNORE with a whitespace character in it, THEN bash won't save to the command history any commands that start with whitespace.

Maybe blevia offered this suggestion for people who aren't using bash but some other shell that has a 'history' command?

Comment by Mozai 119 weeks and 6 days ago

Your point of view

You must be signed in to comment.