From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/28523 Path: main.gmane.org!not-for-mail From: Carey Evans Newsgroups: gmane.emacs.gnus.general Subject: Re: Mailcap behavior not as expected Date: 03 Jan 2000 12:35:46 +1300 Sender: owner-ding@hpc.uh.edu Message-ID: <874scwgi7h.fsf@psyche.evansnet> References: <873dsgnb02.fsf@inanna.danann.net> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035165356 30318 80.91.224.250 (21 Oct 2002 01:55:56 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 01:55:56 +0000 (UTC) Return-Path: Original-Received: from spinoza.math.uh.edu (spinoza.math.uh.edu [129.7.128.18]) by mailhost.sclp.com (Postfix) with ESMTP id B4484D051E for ; Sun, 2 Jan 2000 18:43:52 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by spinoza.math.uh.edu (8.9.1/8.9.1) with ESMTP id RAB05118; Sun, 2 Jan 2000 17:40:04 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sun, 02 Jan 2000 17:38:28 -0600 (CST) Original-Received: from mailhost.sclp.com (postfix@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id RAA04385 for ; Sun, 2 Jan 2000 17:38:18 -0600 (CST) Original-Received: from psyche.evansnet (203-96-156-142.tnt6.paradise.net.nz [203.96.156.142]) by mailhost.sclp.com (Postfix) with ESMTP id 97D1BD051E for ; Sun, 2 Jan 2000 18:36:40 -0500 (EST) Original-Received: from carey by psyche.evansnet with local (Exim 3.11 #1 (Debian)) id 124uXM-0000Cr-00 for ; Mon, 03 Jan 2000 12:35:48 +1300 Original-To: ding@gnus.org In-Reply-To: Per Abrahamsen's message of "02 Jan 2000 16:37:37 +0100" Original-Lines: 18 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/21.1 (Bryce Canyon) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:28523 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:28523 Per Abrahamsen 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..."