{ "content": [ { "type": "text", "text": "# MHLIST (man)\n\n## NAME\n\nmhlist - list information about nmh MIME messages\n\n## SYNOPSIS\n\nmhlist [-help] [-version] [+folder] [msgs] [-file file] [-part number] ... [-type content]\n... [-prefer content] ... [-noprefer] [-headers | -noheaders] [-realsize | -noreal‐\nsize] [-changecur | -nochangecur] [-verbose | -noverbose] [-disposition | -nodisposi‐\ntion]\n\n## DESCRIPTION\n\nThe mhlist command allows you to list information (a table of contents, essentially) about\nthe various parts of a collection of MIME (multi-media) messages.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **FILES**\n- **PROFILE COMPONENTS**\n- **SEE ALSO**\n- **DEFAULTS**\n- **CONTEXT**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "MHLIST", "section": "", "mode": "man", "summary": "mhlist - list information about nmh MIME messages", "synopsis": "mhlist [-help] [-version] [+folder] [msgs] [-file file] [-part number] ... [-type content]\n... [-prefer content] ... [-noprefer] [-headers | -noheaders] [-realsize | -noreal‐\nsize] [-changecur | -nochangecur] [-verbose | -noverbose] [-disposition | -nodisposi‐\ntion]", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [ { "name": "mhbuild", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/mhbuild/1/json" }, { "name": "mhshow", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/mhshow/1/json" }, { "name": "mhstore", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/mhstore/1/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 5, "subsections": [] }, { "name": "DESCRIPTION", "lines": 82, "subsections": [] }, { "name": "FILES", "lines": 2, "subsections": [] }, { "name": "PROFILE COMPONENTS", "lines": 3, "subsections": [] }, { "name": "SEE ALSO", "lines": 2, "subsections": [] }, { "name": "DEFAULTS", "lines": 8, "subsections": [] }, { "name": "CONTEXT", "lines": 4, "subsections": [] } ], "sections": { "NAME": { "content": "mhlist - list information about nmh MIME messages\n", "subsections": [] }, "SYNOPSIS": { "content": "mhlist [-help] [-version] [+folder] [msgs] [-file file] [-part number] ... [-type content]\n... [-prefer content] ... [-noprefer] [-headers | -noheaders] [-realsize | -noreal‐\nsize] [-changecur | -nochangecur] [-verbose | -noverbose] [-disposition | -nodisposi‐\ntion]\n", "subsections": [] }, "DESCRIPTION": { "content": "The mhlist command allows you to list information (a table of contents, essentially) about\nthe various parts of a collection of MIME (multi-media) messages.\n\nmhlist manipulates MIME messages as specified in RFC 2045 to RFC 2049 (See mhbuild(1)).\n\nThe -headers switch indicates that a one-line banner should be displayed above the listing\n(the default).\n\nThe -realsize switch tells mhlist to evaluate the “native” (decoded) format of each content\nprior to listing. This provides an accurate count at the expense of a small delay. In ei‐\nther case, sizes will be expressed using SI prefix abbreviations (K/M/G/T), which are based\non factors of 1000.\n\nIf the -verbose switch is present, then the listing will show any “extra” information that is\npresent in the message, such as comments in the “Content-Type” header.\n\nIf the -disposition switch is present, then the listing will show any relevant information\nfrom the “Content-Disposition” header.\n\nThe option -file file directs mhlist to use the specified file as the source message, rather\nthan a message from a folder. If you specify this file as “-”, then mhlist will accept the\nsource message on the standard input. Note that the file, or input from standard input\nshould be a validly formatted message, just like any other nmh message. It should not be in\nmail drop format (to convert a file in mail drop format to a folder of nmh messages, see\ninc(1)).\n\nBy default, mhlist will list information about the entire message (all of its parts). By us‐\ning the -part, -type, and -prefer switches, you may limit and reorder the set of parts to be\nlisted, based on part number and/or content type.\n\nA part specification consists of a series of numbers separated by dots. For example, in a\nmultipart content containing three parts, these would be named as 1, 2, and 3, respectively.\nIf part 2 was also a multipart content containing two parts, these would be named as 2.1 and\n2.2, respectively. Note that the -part switch is effective only for messages containing a\nmultipart content. If a message has some other kind of content, or if the part is itself an‐\nother multipart content, the -part switch will not prevent the content from being acted upon.\n\nThe -type switch can also be used to restrict (or, when used in conjunction with -part, to\nfurther restrict) the selection of parts according to content type. One or more -type\nswitches part will only select the first match from a multipart/alternative, even if there is\nmore than one subpart that matches (one of) the given content type(s).\n\nUsing either -part or -type switches alone will cause either to select the part(s) they\nmatch. Using them together will select only the part(s) matched by both (sets of) switches.\nIn other words, the result is the intersection, and not the union, of their separate match\nresults.\n\nA content specification consists of a content type and a subtype. The initial list of “stan‐\ndard” content types and subtypes can be found in RFC 2046.\n\nA list of commonly used contents is briefly reproduced here:\n\nType Subtypes\n---- --------\ntext plain, enriched\nmultipart mixed, alternative, digest, parallel\nmessage rfc822, external-body\napplication octet-stream, postscript\nimage jpeg, gif, png\naudio basic\nvideo mpeg\n\nA legal MIME message must contain a subtype specification.\n\nTo specify a content, regardless of its subtype, just use the name of the content, e.g., “au‐\ndio”. To specify a specific subtype, separate the two with a slash, e.g., “audio/basic”.\nNote that regardless of the values given to the -type switch, a multipart content (of any\nsubtype listed above) is always acted upon. Further note that if the -type switch is used,\nand it is desirable to act on a message/external-body content, then the -type switch must be\nused twice: once for message/external-body and once for the content externally referenced.\n\nBy default, the parts of a multipart/alternative part are listed in the reverse order of\ntheir placement in the message. The listing, therefore, is in decreasing order of prefer‐\nence, as defined in RFC 2046. The -prefer switch can be used (one or more times, in order of\nascending preference) to let MH know which content types from a multipart/alternative MIME\npart are preferred by the user, in order to override the default preference order. Thus,\nwhen viewed by mhlist, the ordering of multipart/alternative parts will appear to change when\ninvoked with or without various -prefer switches. The -noprefer switch will cancel any pre‐\nvious -prefer switches. The -prefer and -noprefer switches are functionally most important\nfor mhshow, but are also implemented in mhlist and mhstore to make common part numbering pos‐\nsible across all three programs.\n", "subsections": [] }, "FILES": { "content": "$HOME/.mhprofile The user profile\n", "subsections": [] }, "PROFILE COMPONENTS": { "content": "Path: To determine the user's nmh directory\nCurrent-Folder: To find the default current folder\n", "subsections": [] }, "SEE ALSO": { "content": "mhbuild(1), mhshow(1), mhstore(1)\n", "subsections": [] }, "DEFAULTS": { "content": "`+folder' defaults to the current folder\n`msgs' defaults to cur\n`-headers'\n`-realsize'\n`-changecur'\n`-noverbose'\n`-nodisposition'\n", "subsections": [] }, "CONTEXT": { "content": "If a folder is given, it will become the current folder. The last message selected will be‐\ncome the current message, unless the -nochangecur option is specified.\n\nnmh-1.8 2015-02-06 MHLIST(1mh)", "subsections": [] } } } }