{
    "content": [
        {
            "type": "text",
            "text": "# mailcap.order (info)\n\n## NAME\n\n/etc/mailcap.order - the mailcap ordering specifications\n\n## DESCRIPTION\n\nThe order of entries in the /etc/mailcap file can be altered by editing\nthe /etc/mailcap.order file.  Each line of that file specifies a  pack-\nage  and  an  optional  mime  type.  Mailcap entries that match will be\nplaced in the order of this file.  Entries that  don't  match  will  be\nplaced later.\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION**\n- **LIMITATIONS**\n- **SEE ALSO**\n- **AUTHOR**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "mailcap.order",
        "section": "",
        "mode": "info",
        "summary": "/etc/mailcap.order - the mailcap ordering specifications",
        "synopsis": null,
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [
            {
                "name": "mailcap",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/mailcap/5/json"
            },
            {
                "name": "run-mailcap",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/run-mailcap/1/json"
            },
            {
                "name": "update-mime",
                "section": "8",
                "url": "https://www.chedong.com/phpMan.php/man/update-mime/8/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 29,
                "subsections": []
            },
            {
                "name": "LIMITATIONS",
                "lines": 16,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "AUTHOR",
                "lines": 4,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "/etc/mailcap.order - the mailcap ordering specifications\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "The order of entries in the /etc/mailcap file can be altered by editing\nthe /etc/mailcap.order file.  Each line of that file specifies a  pack-\nage  and  an  optional  mime  type.  Mailcap entries that match will be\nplaced in the order of this file.  Entries that  don't  match  will  be\nplaced later.\n\nExample\nmime-support:*/*\ngv:application/postscript\nnetscape:text/html\nless:text/*\nemacs:text/*\n\nThe  above  would make any entries provided by the mime-support package\n(as found in the /usr/lib/mime/packages directory) take  priority  over\neverything  else.   The gv package will be used over anything else when\nit comes to postscript documents.  Netscape will be used for  any  html\ndocuments and less will be used for any remaining text documents.  How-\never, since neither netscape or less provide for editing documents, any\nedit or compose actions will fall through to the emacs rules.\n\nAfter  modifying  this  file,  be sure to run /usr/sbin/update-mime (as\nroot) to propagate the changes into the /etc/mailcap file.\n\nRemember that this files takes package names and not executable  names.\nIf  you want to define rules that reference specific programs, the best\nway is to include them  in  ~/.mailcap  or  the  user  section  of  the\n/etc/mailcap file.\n",
                "subsections": []
            },
            "LIMITATIONS": {
                "content": "There  is  currently no way to break out a certain type from a wildcard\nrule.  If, for example, both xv and  gimp  were  to  specify  \"image/*\"\nrules, it isn't possible to use xv for gif images but use gimp for jpeg\nimages.\n\nAlso, I would like to add the ability to specify certain actions in the\nrules.  For example, if netscape were to have an edit rule but I wanted\nto use emacs for editing/creating html documents, I could place a  line\nlike\n\nemacs:text/* action=edit|compose\n\nbefore the netscape entry.  The update-mime program would then spit out\nentries such that netscape view rule comes before the emacs  view  rule\nbut have the netscape edit rule comes after the emacs edit rule.\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "mailcap(5) run-mailcap(1) update-mime(8)\n",
                "subsections": []
            },
            "AUTHOR": {
                "content": "The   mailcap.order   specification   was   written   by   Brian  White\n<bcwhite@pobox.com>\n\nDebian Project                   16th Aug 1998                MAILCAP.ORDER(5)",
                "subsections": []
            }
        }
    }
}