Ken Hornstein wrote:
I don't quite understand how you made it work BEFORE 1.6; mhshow wouldn't
do any character conversion, for one. Also, it still won't reflow text
that's too wide.
You could use profile entries like mhshow-charset-iso-8859-1 to run a
script that would run iconv. The script would sometimes get a filename
and sometimes a command from, e.g, the mhshow-show-text/html profile
entry so it wasn't simple. It is much much simpler now so thanks for the
changes. It doesn't reflow text but that's easy from vim with formatprg
set to par.
Mhl already has a facility where you can give it information on what
exactly you want to display. It would make sense to expand this to
encompass various MIME parts. Here are some sample mhl format file
lines, which I've just shot from the hip and haven't thought about them
too much:
body:match,ct=text/plain,inline,ctparam{format}="flowed":display,flowed
This is more flexible than what we have for mhshow (being able to match
content-type and disposition flags). So this could also benefit mhshow.
The trailing ",flowed" could perhaps be handled instead as something
like "filter=par". But, it then starts looking inconsistent with the use of
things like mhshow-show-text/html which is specifying a sort-of external
filter in a different way.
body:match,ct=text/plain,inline:display
body:match,attachment:marker="Part %{part} %{content-type}"
One thought with the marker is that it could be inserted in the form of
a #forw mhbuild directive. You could then choose to include individual
attachments in a reply (or forward). The only problem is that #forw
doesn't support selecting individual message parts: only a whole
message. Currently forwarding messages with attachments is something
that could be better which this might achieve.
Oliver
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers