From: raman@google.com (T.V Raman)
To: emacs-devel@gnu.org
Subject: Re: RFC: Make ~/.mailcap override other settings
Date: Thu, 12 Apr 2018 19:38:56 -0700 [thread overview]
Message-ID: <p91efjjygn3.fsf@google.com> (raw)
In-Reply-To: <87zi28f7cf.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Thu, 12 Apr 2018 23:22:24 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
Simplifying these as you suggest would be a good thing.
Looking at my .custom file, I also have things like
mm-text-html-renderer and associated content-type definitions going back
the days of emacs/w3 -- defined in mm-decode.el -- do those need to be
reconciled as well?
to > Since, well, forever, Emacs has had several sources for information
> about how to display files, like /etc/mailcap, ~/.mailcap and the
> `mailcap-mime-data' variable.
>
> But Emacs' handling of priorities here has never felt quite right, and
> they have historical reasons: In olden days, some distributions put a
> copy of /etc/mailcap into ~/.mailcap, so you didn't really know what the
> system preferences were and what the user's preferences were.
>
> So mailcap.el used the following precedence algorithm:
>
> 1) If it's in `mailcap-mime-data', use that.
>
> 2) If a specific type, say, "image/gif" is in both /etc/mailcap and
> ~/.mailcap, make the ~/.mailcap version win.
>
> 3) If we have less specific types covering the same type, make the most
> specific win. So if /etc/mailcap has "image/gif; xv" and ~/.mailcap has
> "image/*; feh", then "image/gif" wins because it's more specific.
>
> I don't really think this ever made much sense. I think if the user has
> put "image/*; feh" into ~/.mailcap, then that should win.
>
> So I propose to make this change on master. It's backward-incompatible,
> but will lead to a lot less confusion in the years ahead.
>
> What do all y'all think?
--
next prev parent reply other threads:[~2018-04-13 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 21:22 RFC: Make ~/.mailcap override other settings Lars Ingebrigtsen
2018-04-13 2:38 ` T.V Raman [this message]
2018-04-13 11:49 ` Lars Ingebrigtsen
2018-04-13 2:54 ` Mark Oteiza
2018-04-13 8:21 ` joakim
2018-04-13 14:00 ` Eli Zaretskii
2018-04-13 15:40 ` Lars Ingebrigtsen
2018-04-13 17:11 ` Lars Ingebrigtsen
2018-04-14 12:32 ` Lars Ingebrigtsen
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=p91efjjygn3.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@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).