From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Bug in "View as type"?
Date: Wed, 12 Oct 2005 17:43:41 +0200 [thread overview]
Message-ID: <v9fyr63fma.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87u0fmj2e6.fsf@koldfront.dk>
On Wed, Oct 12 2005, Adam Sjøgren wrote:
> On Wed, 12 Oct 2005 14:31:04 +0200, Reiner wrote:
>> On Wed, Oct 12 2005, Adam Sjøgren wrote:
>>> And was prompted like this:
>
>>> View as MIME type: audio/x-wav
>
> [...]
>
>> Can you show me the MIME part headers or MML part you used?
[...]
> Content-Type: application/octet-stream; name=message.wav
> Content-Disposition: attachment; filename=message.wav
Okay, I see. Thanks.
The name can be either in the Content-Type header ("name") or in the
Content-Disposition header ("filename"). I didn't study the relevant
RFCs, but as this function is supposed to be useful when receiving
mails from broken MUAs, I changed it to look at both and use the found
type as DEFAULT instead of INITIAL-INPUT in `completing-read':
* gnus-art.el (gnus-treat-predicate): Add `first'.
(gnus-mime-view-part-as-type-internal): Try to fetch `filename'
from Content-Disposition if Content-Type doesn't provide `name'.
(gnus-mime-view-part-as-type): Set default instead of
initial-input.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2005-10-12 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 21:04 Reiner Steib
2005-10-11 23:04 ` Adam Sjøgren
2005-10-12 12:31 ` Reiner Steib
2005-10-12 13:22 ` Adam Sjøgren
2005-10-12 15:43 ` 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=v9fyr63fma.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).