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:
Send it the easy way, with MIME and everything handled for you by an app that knows best.
There are 2 alternatives - vote for the best!
Another way of sending an attachment.
-s : subject
file : file to be sent
This just reads in a local file and sends it via email. Works with text or binary. *Requires* local mail server.
If you can do better, submit your command here.
You must be signed in to comment.
Does this work over SMTP if the password is not written into the muttrc file? I had trouble with that recently, and I'm wondering if updating mutt will fix it -- I'm running v1.8.
Can't really answer that question, because I've only ever operated scripts in an environment where the smtp gateway was the localhost or a satellite or smarthost that did free relay for the network from which the email originated. I've never needed a script to do smtpauth for me *YIKES*, but if mutt can do that -- which I don't know off the top of my head, more power to you! (It's your own decision to accept the risk of keeping a password in the muttrc file or not; properly chmod'ding it alleviates that risk)