From: Michael McDermott <mmcdermott@mad-computer-scientist.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] printing emails (but not attachments)
Date: Wed, 17 Mar 2010 14:47:16 -0500 [thread overview]
Message-ID: <1268855141-sup-3697@zion> (raw)
In-Reply-To: <1268853590-sup-9103@guava.lanl.gov>
Well, I'm not a dev, but this little wrapper + muttprint is exactly the
kind of thing I've been looking for, from the time I was using pine
until now.
Thanks for posting it.
Excerpts from John Bent's message of Wed Mar 17 14:25:02 -0500 2010:
> Excerpts from John Bent's message of Thu Mar 11 14:11:21 -0700 2010:
> > I've been piping emails into muttprint which works well unless there's
> > a binary attachment. When there's a binary attachment, muttprint
> > prints it and it usually takes tens and tens of pages. Whoops.
> >
> > Anyone else figure out how to print emails but not attachments?
> >
> Well, I'm sure I've once again reinvented the wheel but I wrote my own
> script to print emails without printing binary attachments. It reads an
> email, pipes the headers to muttprint, then pipes text/plain and
> text/html through w3m into muttprint, for everything else it pipes "#
> Attachment: filename (type)." It requires w3m and muttprint to be in
> the user's path.
>
> I'm sorry that it's horribly in violation of sup philosophy but I wrote
> it in python. :( Sorry but my ruby is just barely good enough to do
> 'if' statements in my hooks.
>
> It's attached in case anyone else wants it. I'm scared I really did
> just reinvent the wheel, otherwise I'd add it to the wiki. To print an
> email from sup using this, hit '|' in thread-view-mode to open a pipe
> and then just type sup-print (assuming you've put this attachment in
> your path). I believe all the python imports it uses come standard.
--
Michael McDermott
www.mad-computer-scientist.com
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-03-17 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 21:11 John Bent
2010-03-17 19:25 ` John Bent
2010-03-17 19:47 ` Michael McDermott [this message]
2010-03-18 0:28 ` John Bent
2010-03-17 20:31 ` John Bent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1268855141-sup-3697@zion \
--to=mmcdermott@mad-computer-scientist.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox