Gnus development mailing list
 help / color / mirror / Atom feed
From: Alex Schroeder <kensanata@yahoo.com>
Cc: ding@gnus.org
Subject: Re: Gnus displaying MIME automatically
Date: Mon, 26 Nov 2001 19:53:08 +0100	[thread overview]
Message-ID: <874rnhe54b.fsf@yahoo.com> (raw)
In-Reply-To: <ilu8zctr22q.wl@dhcp128.extundo.com> (Simon Josefsson's message of "Mon, 26 Nov 2001 16:20:29 +0100")

Simon Josefsson <jas@extundo.com> writes:

>> gnus-article-mime-match-handle-function's value is 
>>   undisplayed-alternative
>> gnus-article-mime-part-function's value is nil
>> gnus-buttonized-mime-types's value is nil
>> gnus-display-mime-function's value is gnus-display-mime
>> gnus-ignored-mime-types's value is nil
>> gnus-mime-multipart-functions's value is nil
>> gnus-unbuttonized-mime-types's value is (".*/.*")
>> 
>> Nothing unusual there, right?
>> 
>> >From *Messages*:
>> 
>> Viewing with /usr/bin/w3m -T text/html '%s'
>> Displaying /usr/bin/w3m -T text/html '/tmp/emm.2592im/mm.259Dts'...
>
> You need to frob `mm-automatic-display' to not include text/html, I
> think.
>
>>     Content-Type: multipart/alternative;
>>              boundary="====_ABC0987654321DEF_===="
>
> Or `mm-discouraged-alternatives'.  But...
>
>>     Content-Type: audio/x-wav;
>>              name="stuff.MP3.pif"
>
> ...perhaps a MP3 file is even worse than HTML. (Also, it looks like a
> worm instead of a real MP3 file.)

Yes, I thought so, too.  So much the worse, haha.  But I am not sure
which part actually started the xterm window -- perhaps you are right
and it was the text/html part, not the audio/x-wav part which (I hope)
would have been a button.

Anyway, I have the following variables set, in addition to the ones
mentioned above:

mm-discouraged-alternatives's value is 
("text/html" "text/richtext")

mm-automatic-display's value is 
("text/plain" "text/enriched" "text/richtext" "text/html"
"text/x-vcard" "image/.*" "message/delivery-status" "multipart/.*"
"message/rfc822" "text/x-patch" "application/pgp-signature"
"application/emacs-lisp" "application/x-pkcs7-signature"
"application/pkcs7-signature" "application/x-pkcs7-mime"
"application/pkcs7-mime")

Does it seem plausible then that I got a mail with no text/plain and
only text/html in it -- thus the HTML is displayed.  And the reason is
that text/html is a discouraged alternative -- but if it is the only
alternative, it will be used.  Correct?  The correct solution would be
to remove text/html from mm-automatic-display.  Then I don't have to
specify text/html as a discouraged alternative anymore -- or do I?  Or
would it make more sense to add text/html to
gnus-buttonized-mime-types?

Anyway, is there any other place but the "MIME Commands" node in the
Gnus manual where such things are explained?

Alex.
-- 
http://www.geocities.com/kensanata/
Coffee should be black as hell, strong as death and sweet as love.
	-- Turkish proverb




  reply	other threads:[~2001-11-26 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y9ku1ld2.fsf@yahoo.com>
2001-11-26 15:20 ` Simon Josefsson
2001-11-26 18:53   ` Alex Schroeder [this message]
2001-11-26 19:00     ` Simon Josefsson
2001-11-26 21:07       ` Alex Schroeder

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=874rnhe54b.fsf@yahoo.com \
    --to=kensanata@yahoo.com \
    --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).