From xemacs-m  Thu Aug 28 21:03:07 1997
Received: from firewall2.Lehman.COM (firewall.Lehman.COM [192.147.65.67])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id VAA10873
	for <xemacs-beta@xemacs.org>; Thu, 28 Aug 1997 21:03:07 -0500 (CDT)
Received: from relay.messaging-svcs2.lehman.com by firewall2.Lehman.COM (8.8.6/8.6.12) id WAA27998; Thu, 28 Aug 1997 22:02:58 -0400 (EDT)
Received: from cfdevx1.lehman.com by relay.messaging-svcs2.lehman.com (8.8.5/8.8.5) id WAA20553; Thu, 28 Aug 1997 22:02:28 -0400 (EDT)
Received: from localhost by cfdevx1.lehman.com (4.1/Lehman Bros. V1.6)
	id AA21683; Thu, 28 Aug 97 22:02:27 EDT
Message-Id: <9708290202.AA21683@cfdevx1.lehman.com>
Reply-To: Rick Campbell <rickc@lehman.com>
X-Face: #<@""pDMxa>Mr$Wp[^l7e1RwB6]&7pRp,f=|)6y5?t45X$y(xx.x^?k~;-d>s:SL86Qt82U
 'M!RC3LrDvD/LjiYdGO!:\/\qx?YabgGC9%xw5%0-W05LRvyu9vB9TYk%5PN|C*0WgrXD-L0'g3j;h
X-Windows: Let it get in YOUR way.
Organization: Lehman Brothers Inc.
From: Rick Campbell <rickc@lehman.com>
To: Colin Rafferty <craffert@ml.com>
Cc: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Re: [??] completer.el 
In-Reply-To: Your message of "28 Aug 1997 11:13:20 EDT."
             <ocr4t8apchb.fsf@ml.com> 
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: multipart/signed; protocol="application/pgp-signature";
 boundary="pgp-sign-Multipart_Thu_Aug_28_22:01:59_1997-1"; micalg=pgp-md5
Content-Transfer-Encoding: 7bit
Date: Thu, 28 Aug 1997 22:02:12 -0400
Sender: rickc@lehman.com

--pgp-sign-Multipart_Thu_Aug_28_22:01:59_1997-1
Content-Type: text/plain; charset=US-ASCII

    From: Colin Rafferty <craffert@ml.com>
    Date: 28 Aug 1997 11:13:20 -0400
    
    In Bratislava (and probably before that), in lisp/ilisp, there are
    three versions of completer: completer.el, completer.new.el, and
    completer.no-fun.el.
    
    The first is what we use, and the other two are identical to each
    other.  Does anyone know what this is about?  I use completer regularly, 
    and suffer no problems.

The fact that there are three different versions is just brain-damage
on my part.  In theory, ILISP is backward compatible to something like
18.56, although in practice I seriously doubt that anyone takes
advantage of that.

If FSF's GNU Emacs has the completer built in, we should probably just
drop the ILISP copy altogether in the next release.

			Rick

--pgp-sign-Multipart_Thu_Aug_28_22:01:59_1997-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iQCVAwUBNAYtn1tTztlqB385AQG0HgQAqAqM5Uq7YhmKo0/0QrifqItdf2GRoPcP
dYGOMMJoRbCKF8U9FHLuyJ8DF31K4Ez0HzLZ9GzsO0gHINqmG7NrvCtautzYLHWd
GWUYTrwdbzL8J00ZegdSWcHoq3Fzf/cUKVgHdHzd3CSh0PvbdK8oR+ovJrzj0cBl
ru8T3APjhc4=
=7HpP
-----END PGP MESSAGE-----

--pgp-sign-Multipart_Thu_Aug_28_22:01:59_1997-1--

