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:
Comments can be used directly on the command line so I can save in the history a brief description of what command does.
There are 4 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
It depends on your shell whether this works or not.
I get a syntax error.
There's a slightly better way that works in EVERY common shell (sh, csh, bash, tcsh, zsh, ksh):
ls -alh ;: mycommentWhy would this be a syntax error, inof?
ls -alh #mycommentzsh: bad pattern: #mycomment
Explanation: In zsh, the '#' character introduces a comment only in non-interactive shells (e.g. in scripts). In interactive shells, the '#' charatcer is used for extended pattern matching (globbing). Thus the above syntax error. Well, you *can* configure zsh to accept comments in interactive shells, too, but it's not the default.
The trick with using ':;' instead of '#' always works, with any shell.
This is also helpful for searching using the Ctrl-R button in bash (ie. you can use the comment to label your commands and then find them quickly). A related trick I use is to put a # in the front of a command when I decide I don't want to run it right away. It goes in the history and I can go back to it using Up or Ctrl-R.