I've been working on getting `ilisp' 5.10.1 working, and have it mostly working, plugged into my checkout of the `xemacs-packages' from CVS. I'm back to studying Lisp and Scheme again, and will be using Ilisp some with cmulisp and with guile... (I might try and create an ilisp dialect definition for Maxima as well, though at this point don't know if there's any advantage in using ilisp for that over the plain comint based mode I cobbled together for it last week.) The trouble is that there's some stuff in "ilisp/extra/" that, according to the README there, is `contrib' -- it's not totally GPL compatible since it relies on the online HyperSpec, which is `non-free' (and not redistributable, afaik) What should I do with that? I can make `ilisp' not load it by default, but if, for instance, a Debian package is made of `ilisp', that stuff is maybe supposed to go in a separate package. (blah! What a PITA.) I don't think there's any restriction on redistribution or modification of `hyperspec.el', but it depends on the non-free Common Lisp Hyperspec, I guess. Maybe I should just clam up and put it in the package anyway. Would anyone on earth _really_ freak about that? There is also an issue with the ilisp licence. It's not completely GPL, _yet_... Will someone on the XEmacs Development Team please have a look at it? I'll mail it to you if you like -- I won't include it here. I do not currently have writes to that section of the repository. I think that a patch will be quite large. I can upload a tarball for someone else to commit, or will commit myself if given writes. I will of course make a copy available for approval prior to making that checkin, and think that I'd like for someone who uses `ilisp' to do that. I don't want to check something in that others think of as broken and get people angry with me. I have not even begun to read the `ilisp' codes or even the manual yet. It will take me some time, I imagine. There are a few things needing done with it. They changed the pop up message thing to use a separate frame rather than a popup window. When you load "ilisp", it opens two new frames, rudely. That frame needs a configurable frame properties plist, and there should be an option to make it use a window like it used to. Likely other things should be done. -- Those who do not study Lisp are doomed to reimplement it - Poorly. A few months in the laboratory often saves several hours at the library. mailto:karlheg＠debian.org (Karl M. Hegbloom)