From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37630
Path: main.gmane.org!not-for-mail
From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Newsgroups: gmane.emacs.gnus.general
Subject: Re: Gnus asks where to save MIME part, instead of displaying
 message
Date: Thu, 09 Aug 2001 08:20:38 -0500
Sender: amos@utdallas.edu
Message-ID: <q6my9otcqu1.fsf@spartacus.utdallas.edu>
References: <m2n15brk16.fsf@tuba.localdomain> <87ofprshct.fsf@deneb.enyo.de>
	<m2bslrpnmb.fsf@tuba.localdomain> <871ymn8le2.fsf@deneb.enyo.de>
	<q6md767grex.fsf@spartacus.utdallas.edu>
	<vafd767j6sx.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
	<q6mitfyad3k.fsf@spartacus.utdallas.edu>
	<m1b66byfxaa.fsf@blackbird.mitre.org>
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: main.gmane.org 1035173009 14827 80.91.224.250 (21 Oct 2002 04:03:29 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Mon, 21 Oct 2002 04:03:29 +0000 (UTC)
Return-Path: <amos+lists.ding@utdallas.edu>
Return-Path: <amos+lists.ding@utdallas.edu>
Original-Received: (qmail 21042 invoked from network); 9 Aug 2001 13:21:39 -0000
Original-Received: from ns0.utdallas.edu (129.110.10.1)
  by gnus.org with SMTP; 9 Aug 2001 13:21:39 -0000
Original-Received: from spartacus.utdallas.edu (spartacus.utdallas.edu [129.110.3.11])
	by ns0.utdallas.edu (Postfix) with ESMTP id 1C12B1A029D
	for <ding@gnus.org>; Thu,  9 Aug 2001 08:21:32 -0500 (CDT)
Original-To: ding@gnus.org
In-Reply-To: <m1b66byfxaa.fsf@blackbird.mitre.org> (dsg@world.std.com's
 message of "Wed, 08 Aug 2001 10:20:45 -0400")
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Academic Rigor)
Original-Lines: 24
Xref: main.gmane.org gmane.emacs.gnus.general:37630
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37630

>>>>> On Wed, 08 Aug 2001 10:20:45 -0400,
>>>>> David S Goldberg <dsg@world.std.com> (dsg) writes:

dsg> Does (setq gnus-unbuttonized-mime-types nil) do what you want?

Thanks.  That'll do.  I wonder if a button shouldn't appear if the
article has only 

  Content-Type: text/plain; charset=us-ascii; format=flowed
  Content-Transfer-Encoding: 7bit
  Content-Disposition: inline

and no other parts?  Though, it's not a big deal either way.

Since I set that, I discovered that there are buttons I never knew
about, such as:
 
1.  (*) text/plain          ( ) text/html            
 
That's cool.  Personally I probably wouldn't ever click on the
text/html, but the capability is cool nonetheless.

-- 
Amos