From: Reiner Steib <reinersteib+gmane@imap.cc>
To: info-gnus-english@gnu.org
Subject: Re: mailcap/mime types
Date: Wed, 21 Nov 2007 20:49:23 +0100 [thread overview]
Message-ID: <v98x4rjs58.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <i71wajtoyb.fsf@hilbert.math.albany.edu>
On Wed, Nov 21 2007, William F Hammond wrote:
> 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.
Yes. But that's what Richard asked. ;-)
> 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.
More often it happens when using a broken MUA.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2007-11-21 19:49 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
2007-11-21 19:49 ` Reiner Steib [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=v98x4rjs58.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).