Re: [Nmh-workers] (no subject)

[Ken Hornstein]

>I still don't buy that.  mhlist needs to be consistent with
>the other programs.

Looking back at the original thread ... it seems like I misunderstood you.
When you said, "mhlist is a counterexample", I thought you meant that was
an example of another program that showed the parts reversed (other than
mhstore).  I believe you meant that it just made sense to you the way
mhlist does it.

>> - It doesn't make sense to me, since it's the opposite of the order of the
>>   parts in the actual message (and this isn't, AFAICT, documented
>>   anywhere ... well, okay, I see that you added that in 2013).
>>   Everywhere else, the part numbering is based on actual order.
>
>Can you explain that?  I thought the whole point was that
>the part numbers from mhlist can be used with other programs.

My point was that for any other MIME content, the part ordering is based
on the sequence in the original message.  multipart/alternative is the
exception.  We don't reorder multipart/mixed so that text content is
first and image content is after that, for example.

>Is there anything *wrong* with the current behavior?  I like
>this:
>
>1851       multipart/alternative      11K
>     1     text/html                 8017
>     2     text/plain                3127
>
>I see that part 1 is html so I stop and use that.  I don't
>have to keep looking, or to skip over the sometimes useless
>text/plain.

I guess we'll have to agree to disagree on that; I strongly prefer the
original order, and to me it's not a problem looking at all of the
different alternatives to find the best one.

--Ken