From: Jambunathan K <kjambunathan@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 11212@debbugs.gnu.org
Subject: bug#11212: 24.0.95; mailcap-mime-extensions: Add opendocument formats
Date: Thu, 12 Apr 2012 10:55:39 +0530 [thread overview]
Message-ID: <81sjg9h67g.fsf@gmail.com> (raw)
In-Reply-To: <qud37dyjfk.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 11 Apr 2012 18:47:59 -0400")
Glenn Morris <rgm@gnu.org> writes:
>> Please include OpenDocument extensions to `mailcap-mime-extensions'.
>
> On non MS systems, there is no need, because there are system files
> such as /etc/mime.types that contain this information, and
> mailcap-parse-mimetypes combines these with mailcap-mime-extensions.
My thoughts (See C-h f mailcap-parse-mimetypes)
My machine falls under `mailcap-poor-system-types'. To use the right
mimetype for outgoing attachements, I need to do one of the following:
1. Set the environment "MIMETYPES" and point in to the mimetype file
2. Create one of the following files "~/mime.typ", "~/etc/mime.typ"
and start populating it. (Why do these file names have a typo?)
3. Push an entry via elisp in to `mailcap-mime-extensions'.[2]
Unfortunately info lookup throws up nothing when I search for 1, 2 or 3.
The above options are user-facing and need to be captured in the manual.
It is also desirable that one of the above entries be exposed via custom
group mailcap or mime.
ps: Emacswiki and a quick google search turns up no help around this
area. It is unlikely that an average user would ever do a M-x
mailcap-parse-mimetypes for routine work.
Jambunathan K.
next prev parent reply other threads:[~2012-04-12 5:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 17:32 bug#11212: 24.0.95; mailcap-mime-extensions: Add opendocument formats Jambunathan K
2012-04-11 22:47 ` Glenn Morris
2012-04-11 22:50 ` Glenn Morris
2012-04-12 5:25 ` Jambunathan K [this message]
2012-04-12 6:19 ` Eli Zaretskii
2012-04-12 6:34 ` Jambunathan K
2012-04-12 5:57 ` Eli Zaretskii
2012-04-12 16:32 ` Glenn Morris
2013-11-15 4:36 ` Jambunathan K
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81sjg9h67g.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=11212@debbugs.gnu.org \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).