From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Gnus displaying MIME automatically
Date: Mon, 26 Nov 2001 16:20:29 +0100 [thread overview]
Message-ID: <ilu8zctr22q.wl@dhcp128.extundo.com> (raw)
In-Reply-To: <87y9ku1ld2.fsf@yahoo.com>
At Mon, 26 Nov 2001 00:28:25 +0100,
Alex Schroeder wrote:
>
> I like to have buttons for MIME attachments -- and I like to have some
> mime types inlined automatically. What I don't like is when I open an
> article and a new xterm pops up and stuff happens on my machine. This
> just happened to me for the first time a few minutes ago. My Gnus
> from CVS is a few days old. What changed? I looked through the
> ChangeLog for November but didn't see anything obvious.
>
> 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.)
next parent reply other threads:[~2001-11-26 15:20 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 [this message]
2001-11-26 18:53 ` Alex Schroeder
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=ilu8zctr22q.wl@dhcp128.extundo.com \
--to=jas@extundo.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).