Hide

What's this?

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/

Get involved!

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.

Hide

Stay in the loop…

Follow the Tweets.

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

Subscribe to the feeds.

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Send a local file via email

Terminal - Send a local file via email
mutt your@email_address.com -s "Message Subject Here" -a attachment.jpg </dev/null
2009-12-10 22:49:38
4
Send a local file via email

Send it the easy way, with MIME and everything handled for you by an app that knows best.

Alternatives

There are 8 alternatives - vote for the best!

Terminal - Alternatives
mpack -s "Backup: $file" "$file" email@id.com
2009-12-11 04:03:06
User: sentinel
Tags: mutt
4

Another way of sending an attachment.

-s : subject

file : file to be sent

cat filename | mail -s "Email subject" user@example.com
2009-09-20 01:38:23
Functions: cat mail
Tags: cat mail
2

This just reads in a local file and sends it via email. Works with text or binary. *Requires* local mail server.

echo "see attached file" | mail -a filename -s "subject" email@address
2009-09-21 11:58:49
User: gnpf
Functions: echo mail
Tags: mail
1

if "mail -a" fail, try "mutt -a" or "nail -a"

cat filename | uuencode filename | mail -s "Email subject" user@example.com
2009-09-21 04:13:50
User: amaymon
Functions: cat mail uuencode
Tags: cat mail
0

uuencode the file to appear as an attachment

{ echo -e "$body"; uuencode "$outfile" "$outfile"; } | mail -s "$subject" "$destaddr" ;
2009-12-10 18:08:59
User: glaudiston
Functions: echo mail uuencode
Tags: cat mail
0

on this way we can define the body too

Know a better way?

If you can do better, submit your command here.

What others think

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.

Comment by intuited 240 weeks ago

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)

Comment by linuxrawkstar 240 weeks ago

Your point of view

You must be signed in to comment.

Related sites and podcasts