From: Patrick Totzke <patricktotzke@googlemail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] How to deal with HTML attachments?
Date: Wed, 11 May 2011 15:15:17 +0100 [thread overview]
Message-ID: <1305123066-sup-804@optimusprime> (raw)
In-Reply-To: <BANLkTimu3JNdDCvtX0qN4rbE0ejUHP5ztQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 841 bytes --]
Hi,
I use a mime-hook like this for inline html:
in ~/.sup/hooks$ cat mime-decode.rb :
case content_type
when "text/html"
`/usr/bin/lynx -dump '#{filename}'`
end
To view html when hitting enter you could set your browser in ~/.mailcap:
text/html; firefox %s
best,
/p
Excerpts from Steve's message of Wed May 11 14:53:27 +0100 2011:
> Hi,
>
> A couple days ago, a significant portion of my incoming mail is
> arriving as an HTML attachment only, where previously, HTML formatted
> emails showed up as semi-readable text and also as an attachment. I
> have not messed with sup recently.
>
> How do you recommend dealing with HTML attachments? I hit <enter> on
> the attachment and it says "Couldn't execute view command, viewing as
> text." Any way to bring this up in a web browser?
>
> Thanks.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-05-11 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 13:53 Steve
2011-05-11 14:13 ` Mark Alexander
2011-05-11 14:59 ` Steve
2011-05-11 15:24 ` Mark Alexander
2011-05-11 14:15 ` Patrick Totzke [this message]
2011-05-11 15:40 ` Steve
2011-05-11 14:30 ` Matías Aguirre
2011-05-12 8:30 ` Tero Tilus
2011-05-12 13:21 ` Mark Alexander
2011-05-13 7:39 ` Tero Tilus
2011-05-13 9:55 ` Patrick Totzke
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=1305123066-sup-804@optimusprime \
--to=patricktotzke@googlemail.com \
--cc=sup-devel@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