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/
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.
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
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:
There is 1 alternative - vote for the best!
just use a space to prevent commands from being recorded in bash's history on most systems
If you can do better, submit your command here.
You must be signed in to comment.
This can be done also by preceding the command with a whitespace.
pwd # is logged to historypwd # is not loggedThis can be done also by preceding the command with an extra whitespace.
$ pwd # is logged to history$ pwd # is not loggedThis can be done also by preceding the command with a whitespace. ;)
This can be done also by preceding the command with an extra whitespace.
preceding the command with a whitespace didn't work on centos 5/6
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?