From: dsg@mitre.org (David S. Goldberg)
Subject: ~/mime.types not being parsed automatically
Date: 17 Jul 2000 11:43:03 -0400 [thread overview]
Message-ID: <m1b1z0sepa0.fsf@blackbird.mitre.org> (raw)
I thought it was supposed to be but looking at the sources I don't see
it. Not sure if that should be considered a bug. I'm using CVS 5.8.8
updated about 930AM EDT 2000-07-17. Explicitly calling
(mailcap-parse-mimetype-file (expand-file-name "~/.mime.types"))
does what I need. I assume I need to put it on a hook? What's the
right place to do it?
Thanks,
--
Dave Goldberg
Associate Department Head
G06A
dsg@mitre.org
next reply other threads:[~2000-07-17 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-17 15:43 David S. Goldberg [this message]
2000-07-17 18:31 ` ShengHuo ZHU
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=m1b1z0sepa0.fsf@blackbird.mitre.org \
--to=dsg@mitre.org \
/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).