From xemacs-m  Thu Feb 13 13:34:21 1997
Received: from neal.ctd.comsat.com (exim@neal.ctd.comsat.com [134.133.40.21])
	by xemacs.org (8.8.5/8.8.5) with SMTP id NAA02211
	for <xemacs-beta@xemacs.org>; Thu, 13 Feb 1997 13:34:19 -0600 (CST)
Received: from neal by neal.ctd.comsat.com with local (Exim 1.58 #2)
	id 0vv6vC-0007dl-00; Thu, 13 Feb 1997 14:34:18 -0500
To: xemacs-beta@xemacs.org
Subject: fix tm before release?
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
From: Neal Becker <neal@ctd.comsat.com>
Date: 13 Feb 1997 14:34:16 -0500
Message-ID: <u967zwec07.fsf@neal.ctd.comsat.com>
Lines: 67
X-Mailer: Gnus v5.2.40/XEmacs 20.0

As I understand it, the tm currently in 20.0final is badly broken for
non-mule.  I was unable to use any mime-encoding features of tm, as I
previously reported.  Recompiling tm els didn't fix it.
I have just tried tm-7.105, and it seems to be
OK (so far).

If it's true that mime-encoding is broken for non-mule 20.0, that's a
pretty bad lossage.  Perhaps there's a chance to fix it?

Here's what MORIOKA Tomohiko <morioka@jaist.ac.jp says:

To: Neal Becker <neal@ctd.comsat.com>
cc: xemacs-beta@xemacs.org
Subject: Re: 20.0 mime bug 
In-reply-to: Your message of "13 Feb 1997 07:47:16 EST."
             <u9wwsc6ffv.fsf@neal.ctd.comsat.com> 
Mime-Version: 1.0 (generated by tm-edit 7.104)
Content-Type: multipart/signed; protocol="application/pgp-signature";
 boundary="pgp-sign-Multipart_Thu_Feb_13_22:04:32_1997-1"; micalg=pgp-md5
Content-Transfer-Encoding: 7bit
Date: Thu, 13 Feb 1997 22:04:43 JST
Sender: morioka@jaist.ac.jp
Resent-Message-ID: <"toX_m.0.p4.sip0p"@xemacs>
Resent-From: xemacs-beta@xemacs.org
X-Mailing-List: <xemacs-beta@xemacs.org> archive/latest/2780
X-Loop: xemacs-beta@xemacs.org
Precedence: list
Resent-Sender: xemacs-beta-request@xemacs.org
Resent-Bcc:
Lines: 61
Xref: neal.ctd.comsat.com mail.xemacs:3364 mail.personal:1249

--pgp-sign-Multipart_Thu_Feb_13_22:04:32_1997-1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

>>>>> In <u9wwsc6ffv.fsf@neal.ctd.comsat.com> 
>>>>>=09"Neal" =3D Neal Becker <neal@ctd.comsat.com> wrote:

Neal> >>>>> "MORIOKA" =3D=3D MORIOKA Tomohiko <ISO-2022-JP> writes:

MORIOKA>> [1  <text/plain; ISO-8859-1 (quoted-printable)>]
Neal> >>>>> In <E0vugIK-0006SZ-00@neal.ctd.comsat.com> 
Neal>     >>>>>> "Neal" =3D Neal Becker <neal@ctd.comsat.com> wrote:

Neal>> Do I need to recompile something (This is 20.0 NON mule):

Neal>> Signaling: (invalid-function (macro . #<compiled-function (from "emu=
-e19.elc") (&rest body) "...(6)" [let ((emx-binary-mode t)) body] 3>))
Neal>> as-binary-input-file(("/hosts/neal/local/users/neal/Martin/QPSKPhase=
AmplCorr.H" 915))
Neal>> insert-binary-file-contents-literally("~/Martin/QPSKPhaseAmplCorr.H"=
)
Neal>> mime-insert-encoded-file("~/Martin/QPSKPhaseAmplCorr.H" "7bit")
Neal>> mime-editor/insert-binary-file("~/Martin/QPSKPhaseAmplCorr.H" "7bit"=
)
Neal>> mime-editor/insert-file("~/Martin/QPSKPhaseAmplCorr.H" nil)
Neal>> call-interactively(mime-editor/insert-file)

MORIOKA>>   Maybe emu-19.elc is generated by XEmacs 20.0 with mule.
MORIOKA>> So please recompile it.  Try make all-elc.

Neal> What do we expect all the non-mule xemacs-20 users to do?  We
Neal> aren't giving them the tm source, right?

  I modified emu to fix the problem.  I expect this problem will be
solved in XEmacs 20.1.

