From: Toby Speight <streapadair@gmx.net>
Subject: mailcap-mime-types
Date: 16 Aug 2000 14:45:47 +0100 [thread overview]
Message-ID: <873dk5iak4.fsf@delivery.cam.eu.citrix.com> (raw)
The current version of `mailcap-mime-types' returns only those types
that have appropriate filename extensions in mime.types. Here's one
which also reads mailcap-mime-data to get all types that have handlers
(it still gets those from mime.types - but I don't think it should).
This is useful for `gnus-mime-view-part-as-type', which uses the
result for its (completing-read). I notice that the mml-attach-*
functions use `mml-minibuffer-read-type' - perhaps that could be
shared instead of applying my change?
(defun mailcap-mime-types ()
"Return a list of MIME media types."
(delete nil
(mm-delete-duplicates
(apply 'append
(mapcar 'cdr mailcap-mime-extensions)
(mapcar '(lambda (x)
(and (not (string-match "\\.?\\*" (car x)))
(mapcar '(lambda (x)
(and (not (string-match "\\.?\\*" (car x)))
(cdr (assoc 'type x))))
(cdr x))))
mailcap-mime-data)))))
next reply other threads:[~2000-08-16 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-16 13:45 Toby Speight [this message]
2000-08-16 13:58 ` mailcap-mime-types Toby Speight
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=873dk5iak4.fsf@delivery.cam.eu.citrix.com \
--to=streapadair@gmx.net \
/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).