From: Yair Friedman <yairfr@icts-tech.com>
Cc: Ding List <ding@gnus.org>, Axel Jantsch <axel@imit.kth.se>
Subject: Re: How can MH-E handle application/octet-stream ?
Date: Mon, 16 May 2005 13:41:27 +0200 [thread overview]
Message-ID: <ud5rr4cuw.fsf@icts-tech.com> (raw)
In-Reply-To: <v9vf5kfoer.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 15 May 2005 18:24:12 +0200")
On Sun, 15 May 2005 18:24:12 +0200,
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> [ From the MH-E list; Added Gnus list. ]
>
> On Fri, May 13 2005, Bill Wohler wrote:
>
>> Axel Jantsch <axel@imit.kth.se> writes:
>>> I often get a pdf file (or other well known file types) with
>>> application/octet-stream mime type. In MH-E such an attachment is
>>> displayed as
>>>
>>> [2. Maj.pdf --- application/octet-stream; Maj.pdf]
>>>
>>> Although this is obviously a pdf file, MH-E does not know about it
>>> and does not start a pdf reader.
> [...]
>> MH-E uses gnus to render its multimedia bits. I imagine that Gnus uses
>> the Content-Type header field, not the Content-Disposition field
>> (which contains the filename), for determining what viewer to use.
>
> Yes.
>
>> I've always just saved these files and launched gpdf separately, but I
>> agree that's a pain.
>
> In Gnus, you can use `v gpdf %s RET' on the button to launch gpdf.
>
>> Perhaps a mechanism already exists, or perhaps they would be willing
>> to put in a workaround. If so, please share it with us on mh-e-users
>> mailing list.
Usually in those cases I use gnus-mime-view-part-as-type which is bound to
Key "t" on the attachment button. Most of the time Gnus guesses
correctly the right type (based on extension?), if not auto-completion
works well enough.
next prev parent reply other threads:[~2005-05-16 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505131231.j4DCVCuf026769@bee.imit.kth.se>
[not found] ` <87r7gbhwfl.fsf@olgas.newt.com>
2005-05-15 16:24 ` Reiner Steib
2005-05-16 11:41 ` Yair Friedman [this message]
2005-05-16 11:16 ` Axel Jantsch
2006-07-31 22:39 ` Bill Wohler
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=ud5rr4cuw.fsf@icts-tech.com \
--to=yairfr@icts-tech.com \
--cc=axel@imit.kth.se \
--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).