> That's a really helpful starting point...but it's got a few issues:
>
> if the text component of the MIME message has a "charset" spec,
> the mhshow command will attempt to provide an environment
> (ie., an Xterm window) what that charset can be displayed...
> so the temp file will not contain the message body
Yea, but you can work around that with...
mhshow-charset-iso-8859-1: %s
in ~/.mh_profile.
> all the message headers are included as part of the temp
> file. Strictly speaking, I guess this is accurate in a
> reply, in that those characters were in the original message,
> but it's not the expected behavior.
The script has always behaved the way I expect it to--but note I have
very low expectations about how my nmh usage handles non-ascii, and I
don't think I've ever used my script on a msg that doesn't "mhshow"
as pure ascii.
steve
--
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.