Zach Beane

A short-term fix is to use a Lisp that comes with ASDF 3. That means almost any recent release of any CL, except CLISP.

This should be fixed with the latest client. Please try it and let me know if it helps.

The bundled copy of "rt.asd" also causes problems, is it necessary?

The clone URL is http://git.kpe.io/rt.git On Sun, Jan 17, 2021 at 6:49 PM rtoy wrote: > I'm just too stupid because I can't figure out how to clone the repo....

Yes, the main problem is rt.asd. Incorporating rt.lisp into the test files would avoid the problem.

I have Quicklisp client code for sha256 checking and GPG signature checking in portable CL. See the gpg branch for more info. Right now the hold up is key management...

I don't use cl-launch so it's not an issue for me personally, but you might want to discuss the topic with Fare, the author of cl-launch.

My first instinct is to use simulated network activity in the form of files. The response object is either populated directly from a file, or the drakma result is simulated...

Thanks for the report. I will look into it.

There's no cross-font substitution mechanism. I don't remember exactly what happens when there's a missing glyph - check the docs or source. On Tue, Jan 4, 2022 at 7:01 AM...