Re: RFC: Make ~/.mailcap override other settings

[Mark Oteiza]

Lars Ingebrigtsen <address@hidden> writes:

> 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.

Yikes, this does sound bizarre.

> 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?

+1.  Makes sense to me to have rule precedence follow the usual user-
then system- specific config convention.  The RFC[0] doesn't seem to say
anything about it and (as an example) it looks like that's how (neo)mutt
has done it [1].

[0] https://tools.ietf.org/html/rfc1524
[1] https://raw.githubusercontent.com/neomutt/neomutt/92914f28/rfc1524.c