From: William F Hammond <hammond@csc.albany.edu>
To: info-gnus-english@gnu.org
Subject: Re: mailcap/mime types
Date: Wed, 21 Nov 2007 13:48:12 -0500 [thread overview]
Message-ID: <i71wajtoyb.fsf@hilbert.math.albany.edu> (raw)
In-Reply-To: <v9myt8oggz.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Thu, Nov 08 2007, Richard G Riley wrote:
>> ...
>> What would the .mailcap entry to match this similar to:
>>
>> video/x-ms-wmv;/usr/local/bin/mplayer %s
>
> It would be ...
> application/octet-stream; /usr/local/bin/mplayer %s
But in .mailcap this would cause mplayer to be spawned for all
instances of application/octet-stream, which is a catch-all
content-type for "binary" things of whatever nature.
My sense is that this content-type is used when the content-provider
expects the user to download and save or when the content-provider
does not know what content-type to use.
-- Bill
next prev parent reply other threads:[~2007-11-21 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 18:00 Richard G Riley
2007-11-20 19:38 ` Reiner Steib
2007-11-21 18:48 ` William F Hammond [this message]
2007-11-21 19:49 ` Reiner Steib
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=i71wajtoyb.fsf@hilbert.math.albany.edu \
--to=hammond@csc.albany.edu \
--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).