rpgoldman

I think that's right, but I'm not sure what `--recurse-submodules` does. Anyway, it shouldn't matter for this case since the documentation is not contained in a submodule.

What's gone wrong there is that `git` is interpreting the URL you gave it as the identifier for a thing like a branch that you are trying to fetch, and...

> haven't read the proposal yet, but name it `define-domain` so sly/slime will highlight it right. You can make that as a change in the review.

I wonder if the best thing would be to do the lisp compile once, save the image, and then load it afterwards? There's a way to do this with ASDF,...

I guess we could make a docker image with the built lisp images and then load that? Seems yucky. Also, in the docker script is there any way to save...

Grouping the jobs sounds reasonable -- I split them out because some of them took so much time, and I was having timeout issues.

I have looked into the history more deeply, and it's clear that call and eval terms were added before we took over this code from Dana's group at Maryland. In...

Looking further, I don't see where either `eval` or `call` terms (as opposed to _expressions_) are actually evaluated. I think this would have to happen in the unifier, but there's...

@ko56 I extended your example, and it seems that `eval` terms are not evaluated as the manual implies: ``` lisp (in-package :shop-user) ;; (defdomain tst ;; ( ;; (:op (!mkalist)...

@ukuter -- Do you remember anything about `eval` terms and `call` terms? AFAICT they don't really exist, although `eval` and `call` *expressions* do.