From xemacs-m  Wed Dec 18 00:46:16 1996
Received: from mikan.jaist.ac.jp (mikan.jaist.ac.jp [150.65.8.6])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id AAA02282 for <xemacs-beta@xemacs.org>; Wed, 18 Dec 1996 00:46:15 -0600 (CST)
Received: from is18e0s01.jaist.ac.jp (MORIOKA Tomohiko <morioka@jaist.ac.jp>) by mikan.jaist.ac.jp (8.7.5); id PAA17546; Wed, 18 Dec 1996 15:44:47 +0900 (JST)
Message-Id: <199612180644.PAA17546@mikan.jaist.ac.jp>
X-MUA: mh-e 5.0.2 + tm-mh-e 7.73, tm-view 7.79
X-Face: %yc?f+O/cVKlH*K(H2X/6-d''suf|"1{S:Y0}_9$t@0G3:5M2:-Ck^[8+4^iSLeGc[Ey[WP
 PF]2M#Q9C'u~[=7TJP72J`PZdWvP=s-'-/LhFneC->=ILc~H#$lf2%hLL5U8?psIp`<[>d&@$Pm%~(
 A'"CJ.zuX@TXh\Ra4,b7M&`f"hexU-a4,#X\]Bfp'JI+MGUDRA%_$&UnWAem4}1R"4%uivgn;xFZ%"
 NS>)eCuFYNHc/:W^:{7H>bGQS],x5z[Cy~C;7j#:8y9q|"~9~UWjE<Vm_;)o<Q4S5NweLc(cl7-suY
 NF|_O*xodbmQavM
X-Emacs: Mule 2.4 =?ISO-2022-JP?B?KBskQjlITVUybBsoQik=?=
From: =?ISO-2022-JP?B?GyRCPGkyLBsoQiAbJEJDTkknGyhC?= / MORIOKA Tomohiko <morioka@jaist.ac.jp>
To: Martin Buchholz <mrb@Eng.Sun.COM>
cc: Steven L Baur <steve@miranova.com>, xemacs-beta@xemacs.org
Subject: Re: 20.0b31 bug when running VM... 
In-reply-to: Your message of "Tue, 17 Dec 1996 19:31:20 PST."
             <199612180331.TAA12727@xemacs.eng.sun.com> 
Mime-Version: 1.0 (generated by tm-edit 7.97)
Content-Type: multipart/signed; protocol="application/pgp-signature";
 boundary="pgp-sign-Multipart_Wed_Dec_18_15:44:30_1996-1"; micalg=pgp-md5
Content-Transfer-Encoding: 7bit
Date: Wed, 18 Dec 1996 15:44:46 JST
Sender: morioka@jaist.ac.jp

--pgp-sign-Multipart_Wed_Dec_18_15:44:30_1996-1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

>>>>> In <199612180331.TAA12727@xemacs.eng.sun.com> 
>>>>>=09``Martin'' =3D Martin Buchholz <mrb@Eng.Sun.COM> wrote:

JSC> Hmm, doesn't this mean that the tm shipped with the v20.0b31 will
JSC> only work if 20.0b31 is built with --with-mule (or whatever the
JSC> option is called)?

Martin> Note that the XEmacs maintainers standardly compile all elc's
Martin> using v20-mule (right, Steve?).  Files not containing mule
Martin> characters should work with v20-latin-1.  Or at least, this
Martin> *is* possible.  However, the presence of macros in the lisp
Martin> environment at byte-compile time can make things break, so a
Martin> little care is necessary.

  Maybe better solution is to make a emu module to emulate XEmacs/mule
API.  Then emu-x20 will work for XEmacs 20.0 without mule, and maybe
elc problem will be solved.

;; In future, it is better to prepare builtin pseudo mule feature for
;; XEmacs 20.0 without mule.  Of course, it is better to abolish
;; without mule. :-)  Emacs will be mule, so XEmacs should be mule.

-- 
----------------------------------------------------------------------
MORIOKA Tomohiko <morioka@jaist.ac.jp>
        Japan advanced Institute of Science and Technology, Hokuriku
                Asahi-dai, Tatsu-no-kuchi ch=F4, Nomi, Ishikawa, Japan
------------------------------------------ Frisch, Frei, Fr=F6hlich! ---

--pgp-sign-Multipart_Wed_Dec_18_15:44:30_1996-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP MESSAGE-----
Version: 2.6.3ia
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBMreS2BnuUGV7wuH5AQEyYQQAl3slBxB/TinbN8PMpr97JeCQwYn8o3kG
m6lzGX2qQeN1y+jRnT9sX+50OKheI+F6V3uaerodL61evrNfgQ3cTI9iX34N3rQa
ZxwJsll7Tj+4h8SQjIQjjnFRAWLvsNOM2lSrz9N6Vmv1yftEauMnVgaLvIRtn2BD
3nESSM+L4Nk=
=+4em
-----END PGP MESSAGE-----

--pgp-sign-Multipart_Wed_Dec_18_15:44:30_1996-1--

