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:
This is just a phrase I use to help me remember which way is what when using nice (top, renice, etc.), and not a command, (unless you really want this in your .bash_history to help remind you.) I was using the command `man nice ` way too much just to look up which way is what. This saves 9 keystrokes every time I remember it.
Make sure you downvote me if you think mnemonics sux. Otherwise I hope this helps someone else.
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
The nice command sets the niceness of the command. If a process has a high niceness, it is nice, and it behaves nicely with other processes, in other words, has a low scheduling priority. I think this is where the whole thing originates, but I'm not sure.
I remember it as saying "specify how nice a program will be, to everyone else", thinking that it's more willing to give up its scheduling priority to other processes.
Negative means greedy. Which isn't nice.