From: John Bent <johnbent@lanl.gov>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] printing emails (but not attachments)
Date: Wed, 17 Mar 2010 18:28:04 -0600 [thread overview]
Message-ID: <1268871848-sup-8102@guava.lanl.gov> (raw)
In-Reply-To: <1268855141-sup-3697@zion>
Excerpts from Michael McDermott's message of Wed Mar 17 13:47:16 -0600 2010:
> 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.
>
Glad you like it. Added it to the wiki. Although it seems to make much
more sense to have this functionality inside sup itself. sup already
knows how to decode and display many of the content-types, it already
hides attachments it can't display, and it formats the headers as well.
I tried writing a patch to add a config line for printer command,
add a keystroke for printing, and then have sup pipe the modified email
into the defined printer command, but it's beyond my ruby skills and
beyond the time I spent trying to grok sup.
John
--
Thanks,
John
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-03-18 0:28 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
2010-03-18 0:28 ` John Bent [this message]
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=1268871848-sup-8102@guava.lanl.gov \
--to=johnbent@lanl.gov \
--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