From: Carey Evans <c.evans@clear.net.nz>
Subject: Re: Mailcap behavior not as expected
Date: 03 Jan 2000 12:35:46 +1300 [thread overview]
Message-ID: <874scwgi7h.fsf@psyche.evansnet> (raw)
In-Reply-To: Per Abrahamsen's message of "02 Jan 2000 16:37:37 +0100"
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> When the standard is silent, following the "sample" implementation
> (metamail) is probably the best.
Actually, RFC 1524 *does* specify the behaviour:
} The configuration information will be obtained
} from the FIRST matching entry in a mailcap file, where "matching"
} depends on both a matching content-type specification, an entry
} containing sufficient information for the purposes of the application
} doing the searching, and the success of any test in the "test="
} field, if present.
--
Carey Evans http://home.clear.net.nz/pages/c.evans/
"This is where your sanity gives in..."
next prev parent reply other threads:[~2000-01-02 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-02 8:17 Daniel Pittman
2000-01-02 15:37 ` Per Abrahamsen
2000-01-02 16:12 ` Steinar Bang
2000-01-02 23:35 ` Carey Evans [this message]
2000-04-21 16:22 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874scwgi7h.fsf@psyche.evansnet \
--to=c.evans@clear.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).