{
    "content": [
        {
            "type": "text",
            "text": "# MHLIST (info)\n\n## NAME\n\nmhlist - list information about nmh MIME messages\n\n## SYNOPSIS\n\nmhlist [-help] [-version] [+folder] [msgs] [-file file] [-part number]\n...  [-type content] ...  [-prefer content] ...  [-noprefer]\n[-headers | -noheaders] [-realsize | -norealsize] [-rcache policy]\n[-wcache policy] [-check | -nocheck] [-changecur | -nochangecur]\n[-verbose | -noverbose] [-disposition | -nodisposition]\n\n## DESCRIPTION\n\nThe mhlist command allows you to list information (a table of contents,\nessentially) about the various parts of a collection of MIME (multi-me-\ndia) 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": "info",
        "summary": "mhlist - list information about nmh MIME messages",
        "synopsis": "mhlist [-help] [-version] [+folder] [msgs] [-file file] [-part number]\n...  [-type content] ...  [-prefer content] ...  [-noprefer]\n[-headers | -noheaders] [-realsize | -norealsize] [-rcache policy]\n[-wcache policy] [-check | -nocheck] [-changecur | -nochangecur]\n[-verbose | -noverbose] [-disposition | -nodisposition]",
        "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": 6,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 104,
                "subsections": []
            },
            {
                "name": "FILES",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "PROFILE COMPONENTS",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DEFAULTS",
                "lines": 11,
                "subsections": []
            },
            {
                "name": "CONTEXT",
                "lines": 5,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "mhlist - list information about nmh MIME messages\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "mhlist [-help] [-version] [+folder] [msgs] [-file file] [-part number]\n...  [-type content] ...  [-prefer content] ...  [-noprefer]\n[-headers | -noheaders] [-realsize | -norealsize] [-rcache policy]\n[-wcache policy] [-check | -nocheck] [-changecur | -nochangecur]\n[-verbose | -noverbose] [-disposition | -nodisposition]\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "The mhlist command allows you to list information (a table of contents,\nessentially) about the various parts of a collection of MIME (multi-me-\ndia) messages.\n\nmhlist  manipulates  MIME messages as specified in RFC 2045 to RFC 2049\n(See mhbuild(1)).\n\nThe -headers switch indicates that a one-line  banner  should  be  dis-\nplayed above the listing (the default).\n\nThe  -realsize  switch  tells mhlist to evaluate the \"native\" (decoded)\nformat of each content prior to listing.   This  provides  an  accurate\ncount  at  the expense of a small delay.  In either case, sizes will be\nexpressed using SI prefix abbreviations (K/M/G/T), which are  based  on\nfactors of 1000.\n\nIf  the -verbose switch is present, then the listing will show any \"ex-\ntra\" information that is present in the message, such  as  comments  in\nthe \"Content-Type\" header.\n\nIf  the  -disposition switch is present, then the listing will show any\nrelevant information from the \"Content-Disposition\" header.\n\nThe option -file file directs mhlist to use the specified file  as  the\nsource  message,  rather  than a message from a folder.  If you specify\nthis file as \"-\", then mhlist will accept the  source  message  on  the\nstandard  input.   Note  that  the  file,  or input from standard input\nshould be a validly formatted message, just like any other nmh message.\nIt  should  not  be in mail drop format (to convert a file in mail drop\nformat to a folder of nmh messages, see inc(1)).\n\nBy default, mhlist will list information about the entire message  (all\nof  its  parts).   By using the -part, -type, and -prefer switches, you\nmay limit and reorder the set of parts to be listed, based on part num-\nber and/or content type.\n\nA part specification consists of a series of numbers separated by dots.\nFor example, in a multipart content containing three parts, these would\nbe  named as 1, 2, and 3, respectively.  If part 2 was also a multipart\ncontent containing two parts, these would be named as 2.1 and 2.2,  re-\nspectively.   Note that the -part switch is effective only for messages\ncontaining a multipart content.  If a message has some  other  kind  of\ncontent,  or if the part is itself another multipart content, the -part\nswitch will not prevent the content from being acted upon.\n\nThe -type switch can also be used to restrict (or, when  used  in  con-\njunction  with  -part,  to further restrict) the selection of parts ac-\ncording to content type.  One or more -type switches part will only se-\nlect  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\nthe  part(s)  they  match.   Using  them  together will select only the\npart(s) matched by both (sets of) switches.  In other words, the result\nis  the  intersection,  and  not the union, of their separate match re-\nsults.\n\nA content specification consists of a content type and a subtype.   The\ninitial  list  of \"standard\" content types and subtypes can be found in\nRFC 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, partial, 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\nthe  content,  e.g.,  \"audio\".  To specify a specific subtype, separate\nthe two with a slash, e.g., \"audio/basic\".  Note that regardless of the\nvalues  given  to the -type switch, a multipart content (of any subtype\nlisted above) is always acted upon.  Further note  that  if  the  -type\nswitch  is  used, and it is desirable to act on a message/external-body\ncontent, then the -type switch must be used twice: once for message/ex-\nternal-body and once for the content externally referenced.\n\nBy default, the parts of a multipart/alternative part are listed in the\nreverse order of their placement in the message.  The  listing,  there-\nfore,  is  in  decreasing  order of preference, as defined in RFC 2046.\nThe -prefer switch can be used (one or more times, in order of  ascend-\ning preference) to let MH know which content types from a multipart/al-\nternative MIME part are preferred by the user, in order to override the\ndefault preference order.  Thus, when viewed by mhlist, the ordering of\nmultipart/alternative parts will appear to change when invoked with  or\nwithout various -prefer switches.  The -noprefer switch will cancel any\nprevious -prefer switches.  The  -prefer  and  -noprefer  switches  are\nfunctionally most important for mhshow, but are also implemented in mh-\nlist and mhstore to make common  part  numbering  possible  across  all\nthree programs.\n\nChecking the Contents\nThe  -check  switch tells mhlist to check each content for an integrity\nchecksum.  If a content has such a checksum (specified as a Content-MD5\nheader  field), then mhlist will attempt to verify the integrity of the\ncontent.\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`-nocheck'\n`-headers'\n`-realsize'\n`-rcache ask'\n`-wcache ask'\n`-changecur'\n`-noverbose'\n`-nodisposition'\n",
                "subsections": []
            },
            "CONTEXT": {
                "content": "If a folder is given, it will become the current folder.  The last mes-\nsage  selected will become the current message, unless the -nochangecur\noption is specified.\n\nnmh-1.7.1                         2015-02-06                       MHLIST(1mh)",
                "subsections": []
            }
        }
    }
}