From: Norman Walsh <ndw@nwalsh.com>
To: ding@gnus.org
Subject: State of the art for HTML email
Date: Wed, 23 Feb 2011 19:11:45 -0500 [thread overview]
Message-ID: <m21v2y5m0u.fsf@nwalsh.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]
Hello world,
I apologize for a message that is perhaps only tangentially related
(but as a long time Gnus user, I will assert that it is at least
tangentially related :-) ).
I seem to have accumulated a no longer insignificant minority of
colleagues who insist on sending me HTML email. Mostly I file it in
the bit bucket and figure "fsck 'em", but periodically I actually do
care about the message.
Sometimes "W h" gets the job done. But sometimes the messages include
inline images. In those cases, "W h" often makes things worse. What I
see is something like this:
1. (*) text/plain ( ) text/html
From: John Doe (john.doe@example.org)
To: Some Address (someone@example.com)
What: Issue Created
Link: https://example.com/browse/UOV-235
----
Dear John
I have observed a severe bug...
1. I choose the Frobnitz Widget. Fine so far.
[cid:22DAA184-A92E-4788-9E00-8A0F4184DB75@xxx.example.org]
...
What's the state of the art for dealing with messages like this in
Gnus? Emacs 23 can display inline graphics, so I'd probably be content
if I could just make [cid:xxx] elements resolve to the images.
I'll be honest, I usually just bail at this point and run 'ripmime' in
/tmp and look at the images out-of-band. But that's a PITA.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Labor, n. One of the processes by which
http://nwalsh.com/ | A acquires property for B.--Ambrose
| Bierce
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
next reply other threads:[~2011-02-24 0:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 0:11 Norman Walsh [this message]
2011-02-24 0:18 ` Edward O'Connor
2011-02-24 0:23 ` Norman Walsh
2011-02-24 23:08 ` Dave Goldberg
2011-02-25 15:46 ` Norman Walsh
2011-02-24 7:49 ` Reiner Steib
2011-02-24 11:42 ` Norman Walsh
2011-02-24 7:58 ` Steinar Bang
2011-02-24 12:28 ` Lars Ingebrigtsen
2011-02-24 12:55 ` Recursive require with emacs24? Norman Walsh
2011-02-24 13:11 ` Steinar Bang
2011-02-25 3:39 ` Lars Ingebrigtsen
2011-02-25 15:19 ` Norman Walsh
2011-03-05 12:07 ` Lars Magne Ingebrigtsen
2011-03-05 17:02 ` Andreas Schwab
2011-03-18 14:02 ` Recursive require with nognus? Norman Walsh
2011-03-18 18:42 ` nnir is pwetty kewl! (Was: Recursive require with nognus?) Steinar Bang
2011-03-18 19:24 ` Norman Walsh
2011-03-18 21:40 ` nnir is pwetty kewl! Steinar Bang
2011-03-19 21:34 ` Norman Walsh
2011-03-20 18:12 ` Steinar Bang
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=m21v2y5m0u.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).