François-René Rideau

(My branch could mostly be merged into main stream, as long as the non-working swank-loader-using-asdf is not selected by default, since it's not fully working.)

SBCL is hopeless in this situation. Using CCL on my branch is working better, but still not great: CCL doesn't bork at all, but I get an interesting error everytime...

In previous message, GitHub insert the #<...> as HTML, so you're not seeing the suspicious #<process SLIME Lisp> where just a # appears.

OK, I'm using CCL to help with debugging, since it doesn't crash the same way, but only has an emacs error at each REPL output. Looking at the error, it...

OK, so I got CCL working fine, at least: one issue was that my swank-loader-using-asdf was succeeding at loading all the default _contribs_ via (pushnew 'load-contribs swank::_after-init-hook_), even when SLIME...

OK, I think I fixed the SBCL issue. The way various conditions were handled in sbcl-pprint-patch was way too complex, necessitating special steps from whoever was trying to compile that...

I fixed the SBCL issue in my branch, which I rebased. See my previous message, above. Sorry for the rebasing, if it affects you. I also cleaned up swank-asdf by...

I fixed it by refactoring sbcl-pprint-patch.lisp so that no special magic is needed on the part of whoever tries to compile and/or load it. See the file itself, and swank-sbcl.lisp,...

Wait, I can't reproduce success with SBCL anymore, and I get this error, whether using this minimal slime setup or my complete one. I might have been confused by actually...

How was Gerbil built and installed? Is it from some package manager? If homebuilt, what script or options did you use?