From xemacs-m  Tue Feb  4 19:26:46 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 TAA21745
	for <xemacs-beta@xemacs.org>; Tue, 4 Feb 1997 19:26:45 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcbmz05130; Tue, 4 Feb 1997 20:26:46 -0500 (EST)
Date: Tue, 4 Feb 1997 20:26:46 -0500 (EST)
Message-Id: <QQcbmz05130.199702050126@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: <m2raiwf4qu.fsf@altair.xemacs.org>
References: <199702042330.PAA28471@roy>
	<m2raiwf4qu.fsf@altair.xemacs.org>

Steven L. Baur writes:
 > Damon Lipparelli writes:
 > 
 > > I just re-built XEmacs 20.0 (test1) with MULE enabled (fantastic, by
 > > the way) and was surprised to discover that TM (or a large part of
 > > it) is dumped into XEmacs.  In particular, 'mime-setup is a feature
 > > and this really screws up sending with VM 6.
 > 
 > It is a feature only when you have SunPro enabled.  Otherwise it is
 > not dumped.

O boy.  Is there some recommended way for VM to detect this, so I
can avoid a slew of bug reports?  I really, really don't want to
make VM aggressively remove TM hooks when vm-send-using-mime is
set non-nil, but I may have to in self-defense.  Either that or
make VM bitch unceasingly about it.  Because when it bombs, _I_
am going to get the bug reports.

