Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!nrl-cmf!ames!ucbcad!ucbvax!SPICE.CS.CMU.EDU!Rick.Busdiecker
From: Rick.Busdiecker@SPICE.CS.CMU.EDU.UUCP
Newsgroups: comp.windows.x
Subject: loading CLX in Lucid
Message-ID: <564853236.rfb@SPICE.CS.CMU.EDU>
Date: Wed, 25-Nov-87 10:40:00 EST
Article-I.D.: SPICE.564853236.rfb
Posted: Wed Nov 25 10:40:00 1987
Date-Received: Sun, 29-Nov-87 02:45:43 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Rick.Busdiecker@cs.cmu.edu
Organization: The ARPA Internet
Lines: 17

I get the impression that I have to start up lisp (Lucid Development
Environment Version 2.0.3 on a Sun 3/60) in the CLX code directory in
order for the LOAD-CLX function to work properly.  Is there some way
around this?  Changing the value of *default-pathname-defaults* didn't
to the trick.

Overall, I think that the loading and compiling functions provided in
defsys.lisp in the PCL collection are somewhat superior to those in
defsystem.lisp in CLX; they don't modify the USER package and they
don't require that you be in a particular directory.  Perhaps the CLX
authors should incorporate these facilities into CLX?

Lest I come across as totally critical, I'd like to compliment the
authors on a really nice interface to X11.  CLX totally blows away the
C call-out interface to X10 that I used on an IBM-RT.

			Rick