From xemacs-m  Fri Mar 21 01:18:19 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 BAA00540
	for <xemacs-beta@xemacs.org>; Fri, 21 Mar 1997 01:18:17 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQchuj13779; Fri, 21 Mar 1997 02:18:16 -0500 (EST)
Date: Fri, 21 Mar 1997 02:18:16 -0500 (EST)
Message-Id: <QQchuj13779.199703210718@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: char-before (Re: XEmacs 19.15-b102 is released)
In-Reply-To: <m2lo7hlnqi.fsf@altair.xemacs.org>
References: <199703210649.PAA08954@mikan.jaist.ac.jp>
	<m2lo7hlnqi.fsf@altair.xemacs.org>
X-Mailer: VM 6.21 under 19.15 XEmacs Lucid (beta101)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Steven L Baur writes:
 > MORIOKA Tomohiko writes:
 > 
 > > char-before: a built-in function.
 > 
 > > Return character in current buffer preceding position POS.
 > > POS is an integer or a buffer pointer.
 > > If POS is out of range, the value is nil.
 > > If `enable-multibyte-characters' is nil or POS is not at character boundary,
 > > multi-byte form is ignored, and only one byte preceding POS
 > > is returned as a character.
 > 
 > > (char-before POS)
 > 
 > O.K.  Do I need to make a dummy definition of
 > enable-multibyte-characters for compatibility?  It sounds too
 > dangerous to actually implement.

Of what use would the variable be if it doesn't change any
behavior?  I think you should leave it out.

