1) when you use show on a range of emails, and if they're all
non-mime ones, output is very pleasant and comfortable - every
message is indented and given a nice header with its number (it's
very useful for replies). It's very convenient to use with 'pick',
for example to read whole thread in mailing list with "show `pick
-subj <subj>`". But whenever even one message is MIME, even if it's
only text/plain - all chain starts to be processed with mhshow.
So, that's not _exactly_ true. You can, for example, add -nocheckmime
to show to suppress that behavior (also, at least for 1.5, set NOMHNPROC
in your environment). Of course you get no decoding of the message body
when you do that.
I managed to escape from <press enter> for headers with mhshow:
-nomoreproc, but I can't get the same eye-plesant result as with
non-mime messages.
Does anyone ever scripted a solution for this with metamail or
anything like this? Or what can you advice to read a chain of MIME
messages in a manner 'show' does (with messages numbers/indents)?
Sigh. It's unfortunate, but right now "mhshow" pretty much sucks. My plan
is to make things much better for 1.6 (but it still won't be exactly where
I want). Right now there is no good answer in 1.5 (or even in the git
tree).
2) When I reply with non-english text to an email, and attach a file
to the reply, final message is a multipart MIME, and text part is
octet-stream, I checked git (1.5 here) - seem it's fixed there,
much thanks for that, nevertheless, is it possible to make those
'text' parts of the reply as 'Content-Disposition: inline' somehow?
Let me understand you, so there's no confusion. You're saying that you
repl to a message, you include non-ASCII characters in your reply text,
you use the "attach" command, and the text part of your message ends up as
an application/octet-stream?
Okay, yeah, that's also unfortunately the default behavior in 1.5 and
we didn't fix that until after 1.5 was released. The attach system has
been totally revamped and should be a lot better for 1.6, but I think
right now your only solution is to manually construct mhbuild directives
for the files you want to attach and then run "mime" at the whatnow?
prompt; if you do that, things should work out correctly.
--Ken
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers