From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: mml bug?
Date: Tue, 3 Oct 2000 09:39:55 -0400 [thread overview]
Message-ID: <200010031339.e93Ddtf05605@zsh.2y.net> (raw)
In-Reply-To: <i5k4s2ujcwn.Wong@gromit.ph.surrey.ac.uk>
Paul Stevenson <p.stevenson@surrey.ac.uk> writes:
> I've just upgraded to latest CVS and I notice that when I attach a
> file and am prompted for the Content-Type, then press tab to see the
> list of known types, there are a few bogus entries (mangled duplicates
> of postscript and pdf)
Those entries come from mailcap-mime-data, mailcap-mime-extensions,
mailcap files and mime-types files. What does evaluating
(mailcap-mime-types) say?
ShengHuo
next prev parent reply other threads:[~2000-10-03 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-03 13:02 Paul Stevenson
2000-10-03 13:39 ` ShengHuo ZHU [this message]
2000-10-03 15:12 ` Paul Stevenson
2000-10-03 15:25 ` ShengHuo ZHU
2000-10-03 15:30 ` Paul Stevenson
2000-10-03 15:43 ` ShengHuo ZHU
2000-10-04 8:28 ` Paul Stevenson
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=200010031339.e93Ddtf05605@zsh.2y.net \
--to=zsh@cs.rochester.edu \
/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).