From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Giving priority to wildcard MIME types
Date: Mon, 22 Feb 2016 23:31:40 +0100 [thread overview]
Message-ID: <871t841inn.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <m2d1ro2xsg.fsf@eno.apple.com>
Dave writes:
> The problem is, mailcap-possible-viewers is designed to always list the
> non-wildcard matches (which are in mailcap-mime-data) first, which means
> I have to manually create “open %s” lines in ~/.mailcap for each mime
> type in that list. There's got to be a better way... doesn't there?
I think this was discussed recently¹, leading to:
· https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22684
Best regards,
Adam
¹: http://thread.gmane.org/gmane.emacs.gnus.user/18079/
--
"Jeg har læst alt hvad google kan finde." Adam Sjøgren
asjo@koldfront.dk
prev parent reply other threads:[~2016-02-22 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 22:19 Dave Abrahams
2016-02-22 22:31 ` Adam Sjøgren [this message]
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=871t841inn.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.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.
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).