[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Nmh-workers] Displaying/Replying to HTML emails

From: Arun Bhalla
Subject: [Nmh-workers] Displaying/Replying to HTML emails
Date: Tue, 23 Nov 2004 17:39:42 -0600

Along the lines of the recent wishlist items, I'm wondering if anyone
(or nmh 1.1, even) has a good solution for handling HTML emails.  I
know that nmh used to have a problem with not really knowing how to
handle showing a certain kind of multipart message (I can't find an
example at the moment...)  even though the message may have contained
text/plain and text/html parts, and I wish nmh would give me the
option to favor text/plain parts of a multipart/alternative.  (My
understanding is that nmh 1.1 has corrected one or both, or that it's
in the works...)

In addition, like many of you, I'm sure, I have to read and respond to
emails containing text/html parts.  Reading isn't so bad since I just
pipe it through lynx in my .mh_profile, although sometimes I'd rather
have it default to text/plain (see above).  But replying can be nasty,
especially if there's only a text/html part (seemingly common from Hotmail
users) and no text/plain part.  I'd rather not have any non-text parts
in the reply body if there's a text/plain part; if the text/html part is
the only text part, I'd rather have it stripped of tags.  I might argue
that some nmh utility should do all of that for me, but if someone can
recommend some scripts and .mh_profile configurations, I certainly
wouldn't mind.

The deluge of HTML email has pushed me towards mutt or other new MUAs,
but I've managed to suppress the urge so far.

Completely unrelated to that, I use repl(1) to forward emails instead
of forw(1).  If I remember correctly, I made that switch because forw(1)
didn't seem to automatically include a subject extracted from the source email,
and it seems that's an inherent shortcoming to forw(1).  I'm just saying --
I'm reasonably happy with my workaround, and if it's been fixed, I'll dump
my workaround; if not, maybe it should be corrected, and maybe I'll jump
on it.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]