[Nmh-workers] Ordering of Parts by mhlist.

Hi, $ mhlist msg part type/subtype size description 19696 multipart/alternative 4785 1 text/html 2787 2 text/plain1680 $ The email has subtype plain first, then html. I know this from show(1) so

Re: [Nmh-workers] Ordering of Parts by mhlist.

msg part type/subtype size description 19696 multipart/alternative 4785 1 text/html 2787 2 text/plain1680 $ The email has subtype plain first, then html. I know this from show(1) so it's then a bit odd

Re: [Nmh-workers] Ordering of Parts by mhlist.

Ralph wrote: Hi, $ mhlist msg part type/subtype size description 19696 multipart/alternative 4785 1 text/html 2787 2 text/plain1680 $ The email has subtype plain first, then html. I

Re: [Nmh-workers] Ordering of Parts by mhlist.

Hi David, mhlist(1) doesn't mention order AFAICS. Personally, I'd prefer the email's order rather than add a layer of change for what seems little gain. I believe it's to convey the order of preference of RFC 1341, Sec. 7.2.3. Given that, I think the order make sense. Thanks for the

Re: [Nmh-workers] Ordering of Parts by mhlist.

Thanks for the reference. I can see that makes sense when displaying the parts, baring the best type based on the user's... preferences, but mhlist(1) says list information about MIME messages and I'm not so sure it's intended by the RFC's authors then. Perhaps it's just a side-effect of the

Re: [Nmh-workers] Relative Message Numbers

david wrote: Ralph wrote: Hi Paul, as a convenience feature when typing negative offsets, foo:-n and foo=-n can be entered as foo::n and foo==n respectively. I dislike this. Must be my preference for Python's `one way to do it' over Perl's `there must still be one