From: Ben Bacarisse <ben.lists@bsb.me.uk>
To: info-gnus-english@gnu.org
Subject: Gnus seems to not understand video/* syntax in mailcap files.
Date: Sat, 13 Feb 2016 20:55:20 +0000 [thread overview]
Message-ID: <87io1s5o07.fsf@bsb.me.uk> (raw)
My system is currently set up so that gnus happens to use mplayer to
open video mime parts but I'd like it, and other mailcap aware programs,
to use something else. So I put the line
video/*; totem %s
into ~/.mailscap. Checking with run-mailcap shows it to be working as
expected, but gnus continues to use mplayer. However, if I put
video/quicktime; totem %s
in there instead, all is well for that one type -- gnus uses totem for
quicktime files (but, of course, mplayer for every other video type).
The same happens if the line is in the /etc/mailcap "user section":
video/* does not work but video/quicktime does.
Is this as per design, or is it a bug?
--
Ben.
next reply other threads:[~2016-02-13 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 20:55 Ben Bacarisse [this message]
[not found] <mailman.4594.1455396972.843.info-gnus-english@gnu.org>
2016-02-14 2:37 ` Lars Ingebrigtsen
2016-02-14 16:48 ` Ben
2016-02-15 4:26 ` Lars Ingebrigtsen
2016-02-15 11:19 ` Ben
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=87io1s5o07.fsf@bsb.me.uk \
--to=ben.lists@bsb.me.uk \
--cc=info-gnus-english@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.
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).