From xemacs-m  Wed Feb  5 16:16:08 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id QAA06559
	for <xemacs-beta@xemacs.org>; Wed, 5 Feb 1997 16:16:06 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcbqf23431; Wed, 5 Feb 1997 17:16:05 -0500 (EST)
Date: Wed, 5 Feb 1997 17:16:05 -0500 (EST)
Message-Id: <QQcbqf23431.199702052216@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Re: XEmacs 20.0 w/ MULE enables TM
In-Reply-To: <m2afpjaqef.fsf@altair.xemacs.org>
References: <9702051226.AA12764@lspsun16.epfl.ch>
	<199702051318.WAA06694@mikan.jaist.ac.jp>
	<QQcbpk19103.199702051701@crystal.WonderWorks.COM>
	<m2afpjaqef.fsf@altair.xemacs.org>

Steven L. Baur writes:
 > Kyle Jones writes:
 > 
 > > This defision need be so hard.  If the decision has been made
 > > that TM will be the MIME viewer of choice under XEmacs, then turn
 > > VM's MIME handling off by default in XEmacs.  I have no problem
 > > with this.  Problem solved?
 > 
 > You've lost on me on this discussion.
 > 
 > TM is dumped with XEmacs only on Sun with SunPro support enabled
 > and only when MULE support is enabled.  I consider the current
 > behavior a bug -- it shouldn't be standardly dumped with XEmacs in any
 > environment, but I don't maintain the SunPro stuffs.

I don't think the issue was that it was dumped, but rather than
it was turned on by default in mail-mode.  Bad for VM's
out-of-the-box configuration, but good for RMAIL and anything
else without builtin MIME support.  My point, turn off VM's MIME
composition code in the version that's shipped with XEmacs.
Poof, problem solved?  I don't know; no one answered.

We could just not ship VM with XEmacs, since I'm such a bad boy
and troublemaker for ignoring TM, and that would solve the
problem, too.  This has the added benefit of my not getting the
same bug reports for VM 6.15 for the next five years, because the
19.15 release cast it in stone for thousands of lusers who only
upgrade their software when a disk catches fire. 5/8 :)

