From xemacs-m  Fri Apr  4 06:22:40 1997
Received: from ns.jsys.co.jp (ns.jsys.co.jp [202.33.240.82])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id GAA13837
	for <xemacs-beta@xemacs.org>; Fri, 4 Apr 1997 06:22:37 -0600 (CST)
Received: from cosmos.jsys.co.jp (cosmos.jsys.co.jp [172.31.80.5])
	by ns.jsys.co.jp (8.8.5/8.8.5) with ESMTP id VAA27568
	for <xemacs-beta@xemacs.org>; Fri, 4 Apr 1997 21:22:38 +0900 (JST)
Received: from j-04110.jsys.co.jp (j-04110.jsys.co.jp [172.31.49.72])
	by cosmos.jsys.co.jp (8.8.5/8.8.5) with ESMTP id VAA13042
	for <xemacs-beta@xemacs.org>; Fri, 4 Apr 1997 21:22:37 +0900 (JST)
Received: (from ienaga@localhost) by j-04110.jsys.co.jp (8.8.5/3.5Wpl2) id VAA07392; Fri, 4 Apr 1997 21:22:34 +0900 (JST)
Sender: ienaga@j-04110.jsys.co.jp
To: xemacs-beta@xemacs.org
Subject: Re: XEmacs futures (Countdown to 20.1 and possible 19.16)
References: <m2208r57zr.fsf@altair.xemacs.org>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Kazuyuki IENAGA <ienaga@jsys.co.jp>
Date: 04 Apr 1997 21:22:32 +0900
In-Reply-To: Steven L Baur's message of 04 Apr 1997 03:43:04 -0800
Message-ID: <rysbu7v9dvb.fsf@skywalk.jsys.co.jp>
Lines: 53
X-Mailer: Gnus v5.4.18/Emacs 19.34

Japanese related things.

Steven L Baur <steve@miranova.com> writes:

> 4.  There are various MULE related crash reports that need
>     investigation (Steve Dunham's in particular).
> 
> If I've forgotten anything, now is the time to speak up.  I intend to
> release 20.1 in a couple weeks.  See the README on the beta site for
> schedule.

I had two problems with 20.1-b10 on FreeBSD 2.2.1, Motif (SWiM).

1.  When I got kinput2 (an input method for X) running, and invoked
XEmacs, then XEmacs's window began to shrink, then at last got fatal
error (13).

Lisp backtrace follows:

  # (catch #<INTERNAL EMACS BUG (opaque, size=4) 0x2dcb40> ...)
  # (unwind-protect ...)
  # (unwind-protect ...)
  # bind (inhibit-quit)
  input-pending-p()
  command-line-1()
  # bind (command-line-args-left)
  command-line()
  # (unwind-protect ...)
  normal-top-level()
  # (condition-case ... . error)
  # (catch top-level ...)

Also, to get XEmacs comes to visible, it takes very long time around 1 
or 2 minutes.

Is it X-resource related thing?


2.  When the language-environment is "ja", kinsoku-ascii-bol do not
seem to work.  Of course, it's in *fill-mode*.

When I wrote a text including Japanese, close to EOL, and put
comma(',') substitute for Japanese comma, then the comma was
positioned to BOL.
I prefer to use kinsoku-ascii-bol/eol characters if I'm writing
Japanese  and I know some people also do it.

Then I set kinsoku-ascii to t to make things correct, I got strange
behavior that the blank lines were inserted after the comma while I
put SPACE key!!

-- 
kazz

