From xemacs-m  Thu Feb  6 12:12:01 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 MAA19103
	for <xemacs-beta@xemacs.org>; Thu, 6 Feb 1997 12:11:59 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcbtg17896; Thu, 6 Feb 1997 13:12:00 -0500 (EST)
Date: Thu, 6 Feb 1997 13:12:00 -0500 (EST)
Message-Id: <QQcbtg17896.199702061812@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: <m2eneu4ow7.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>
	<QQcbqf23431.199702052216@crystal.WonderWorks.COM>
	<m2eneu4ow7.fsf@altair.xemacs.org>

Steven L. Baur writes:
 > Kyle Jones writes:
 > 
 > > 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.
 > 
 > O.K.  Could somebody please send me a patch?  I've been silent on a
 > couple of threads because I've been tracking down serious problems
 > with 19.15 the last couple of days.

VM 6.12 defaults vm-send-using-mime to nil if (featurep 'mime-setup).
Does something similar need to be for the display side?

(TM-VM users, this question is directed to you.)

