From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: Improper handling of some mime types
Date: Thu, 14 Feb 2002 13:00:42 -0500 [thread overview]
Message-ID: <vxk3d04c59x.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <m26650dmsa.fsf@kurt.swanson> (Kurt Swanson's message of "14 Feb 2002 08:57:09 -0800")
(setq gnus-unbuttonized-mime-types nil)
This will always show you buttons, wherever buttons are possible.
(setq gnus-mime-display-multipart-related-as-mixed t ; bug workaround.
This will step around the (w3?) problem of multipart/related image
display.
Or, rather than using the second of these, just hit `C-d' on such a
message, and see how Gnus breaks the message up.
prev parent reply other threads:[~2002-02-14 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2wuxgg8ab.fsf@kurt.swanson>
2002-02-14 8:35 ` Kai Großjohann
[not found] ` <m26650dmsa.fsf@kurt.swanson>
2002-02-14 17:25 ` Kai Großjohann
[not found] ` <m2664zdipf.fsf@kurt.swanson>
2002-02-14 18:38 ` ShengHuo ZHU
2002-02-14 17:32 ` ShengHuo ZHU
2002-02-14 17:39 ` David S. Goldberg
2002-02-14 17:54 ` David S. Goldberg
[not found] ` <m2adubdis3.fsf@kurt.swanson>
2002-02-15 9:09 ` Kai Großjohann
2002-02-14 18:00 ` Karl Kleinpaste [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=vxk3d04c59x.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.com \
/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).