%{...} in mailcap (was: bugs in mailcap (patch: 93-zsh3))

[Shenghuo ZHU <zsh@cs.rochester.edu>]

>>>>> "LMI" == Lars Magne Ingebrigtsen <bugs@gnus.org> writes:

>> Here the patch. By the way, I guess mm-display-external do not handle
>> %-sequences like %{name}, %{patchnumber}.

LMI> No, it doesn't -- I didn't even know that one could do that.  Is the
LMI> mailcap format specified anywhere?

The following is cited from mailcap manual of RedHat 6.0 (by Nathaniel
S. Borenstein).

,--------
|        The "command" field is any UNIX command ("cat %s"  in  the
|        above example), and is used to specify the interpreter for
|        the given type of message.  It will be passed to the shell
|        via  the  system(3)  facility.  Semicolons and backslashes
|        within the command must be quoted  with  backslashes.   If
|        the  command  contains  "%s", those two characters will be
|        replaced by the name of a file that contains the  body  of
|        the  message.  If  it  contains "%t', those two characters
|        will be replaced by the content-type field, including  the
|        subtype,  if  any.   (That  is,  if  the  content-type was
|        "image/pbm;  opt1=something-else",  then  "%t"  would   be
|        replaced  by "image/pbm".)   If the command field contains
|        "%{" followed by a parameter name and a closing "}",  then
|        all  those characters will be replaced by the value of the
|        named parameter, if any,  from  the  Content-type  header.
|        Thus,  in the previous example, "%{opt1}" will be replaced
|        by "something-else".  Finally, if the command contains "",
|        those two characters will be replaced by a single % ch
| 
|        aracter.  (In fact, the backslash can be used to quote any
|        character, including itself.)
`--------


-- 
Shenghuo