From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11212@debbugs.gnu.org, kjambunathan@gmail.com
Subject: bug#11212: 24.0.95; mailcap-mime-extensions: Add opendocument formats
Date: Thu, 12 Apr 2012 12:32:19 -0400 [thread overview]
Message-ID: <i1lim052ss.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83r4vt4hls.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Apr 2012 08:57:51 +0300")
Eli Zaretskii wrote:
> This file seems to come from mime-support, which is a Debian package.
> Do other Posix systems, whether other GNU/Linux or Unix, also have
> this file?
I'm 99% sure all halfway modern GNU/Linux systems have such files.
Eg, Red Hat based ones do. Less sure about any other Unix.
mailcap-poor-system-types suggests they do.
> OTOH, if we want to rely on this file, then why do we have a non-empty
> mailcap-mime-extensions at all? And why adding a few more entries to
> that list should be rejected?
I'm not rejecting anything; but since this issue mainly affects MS
Windows it's not a high priority for me personally to change it.
mailcap-mime-extensions is weird (IMO), in that there is a default
(which is a defcustom) that gets modified behind the user's back. It
would be cleaner to separate it out into different variables.
An empty one for the user's customizations, one that gets the system
entries added to it, and a fallback one for systems without databases.
I think it's fine to add many more entries to the last one.
Or stick a mime-types file in the Emacs etc directory if that is easier.
next prev parent reply other threads:[~2012-04-12 16:32 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
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 [this message]
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=i1lim052ss.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=11212@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kjambunathan@gmail.com \
/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).