>>>>> "Raymond" == Raymond Toy <toy(a)rtp.ericsson.se> writes:
>>>>> "Andreas" == Andreas Jaeger <aj(a)suse.de> writes:
Andreas> What is _not_ in there (yet)
Andreas> - latest ilisp (server unavailable/volunteer need)
Raymond> Just a note: I tried the latest version. I couldn't get it to do
Raymond> anything useful. There was some error about processes or something,
Raymond> and the inferior lisp never got started. I didn't want to spend
Raymond> anymore time on it so I reverted back the existing version.
Raymond> Perhaps others have had better luck than I,
Found the problem I was having. I extracted the new ilisp package
into ~/.xemacs/xemacs-packages/lisp/ilisp. However, when I run it,
ilisp goes looking for where it came from via load-path, and my
load-path doesn't include ~/.xemacs/xemacs-packages/lisp/ilisp. Thus,
I was getting a mix of old and new ilisp files.
Once I added that path to my load-path, my problems went away.
I think ilisp 5.9.2 is OK. It works just fine for me.
The question is how should ilisp go looking for where it was loaded
from. It currently tries to find itself by looking at all the entries
in load-path. Should it look in the package path first, and then fall
back to load-path?