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:
when your terminal session seems unrensponsive (this normally happen after outputting some binary data directly on your standard output) it may me saned by hitting:
CTRL+J tput sgr0 CTRL+J
Note: don't press the Enter key, just ctrl+j
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
just reset will do
resetBe simple :D
reset doesn't always work as expected. With Kermit-95 terminal emulator for example, it'l mess up the screen.
^j is the ASCII sequence for the Enter key. Pressing it first clears your keyboard buffer before running the command.
reset didn't work for me when I accidentally tried to vi a command, then ; another. This was the only example I found to work.