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:
Note the extra space before the command (I had to put it as an underscore since the website eats up preceding spaces). That's all it takes. Now if you check your history with "$ history", it wont show up.
There are 3 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
This doesn't seem to work in Centos 5
[root@centos5 /]# cd /home
[root@centos5 home]# cd /
[root@centos5 /]# history|tail -n 3
1018 cd /home
1019 cd /
1020 history|tail -n 3
[root@centos5 /]#
(btw, the extra space is in there...it just doesn't show up in these comments)
Doesn't work in Fedora 10.
This works with Opensuse 11 and midget_donkey rocks!!!
Works in Ubuntu 8.10. Upon checking the bash man page, you need the environment variable HISTCONTROL=ignoreboth or =ignorespace.
My bad for not noting this. Also you can have more control by using HISTIGNORE
other (possibly helpful) info at this duplicate:
http://www.commandlinefu.com/commands/view/1512/execute-a-command-without-saving-it-in-the-history