Re: [Nmh-workers] mhlist output format

[Paul Fox]

a while ago i suggested making a bunch of changes mhlist, to make the
output more parseable.  ken correctly pointed out that i might be
going a bit too far too quickly, and i adjusted my wrapper script to
be able to work with the existing output -- the whitespace parsing
issues weren't that hard to deal with after all.

but there's one aspect of the mhlist output that i think could change
readily enough.  currently, mhlist will truncate certain string fields
to keep the output tabular.  in particular, content-types are
truncated to 24 characters, content-descriptions to 36, and rfc-822
comments on a content-type to 65.

the content-type limit gets hit pretty easily with application types,
e.g. "application/x-zip-compre".

i propose eliminating any of the truncations if "-verbose" is given. 
example output below -- all of the above-mentioned truncations occur
in part 2.

output without -verbose is unchanged:

$ mhlist
 msg part  type/subtype              size description
   4       multipart/signed           13K
     1     text/plain                4608
     2     application/pkcs7-signat  5958 S/MIME Cryptographic Signature with


old output with -verbose, fields truncated:

$ mhlist -verbose
 msg part  type/subtype              size description
   4       multipart/signed           13K
             protocol="application/pkcs7-signature"
             micalg="sha-1"
             boundary="----=_Part_2919_383128135.1401281510426"
     1     text/plain                4608
             charset="UTF-8"
             format="flowed"
             delsp="Yes"
     2     application/pkcs7-signat  5958 S/MIME Cryptographic Signature with 
             name="smime.p7s"
             smime-type="signed-data"
             (this is a very long and boring comment that no one really ever w


new output with -verbose, no truncations:

$ uip/mhlist -verbose
 msg part  type/subtype              size description
   4       multipart/signed           13K
             protocol="application/pkcs7-signature"
             micalg="sha-1"
             boundary="----=_Part_2919_383128135.1401281510426"
     1     text/plain                4608
             charset="UTF-8"
             format="flowed"
             delsp="Yes"
     2     application/pkcs7-signature  5958 S/MIME Cryptographic Signature 
with an augmented description
             name="smime.p7s"
             smime-type="signed-data"
             (this is a very long and boring comment that no one really ever 
wants to see, but there you have it)


any objections to this?

paul
=----------------------
 paul fox, address@hidden (arlington, ma, where it's 44.4 degrees)