Ethan Blanton

[This paramiko issue](https://github.com/paramiko/paramiko/issues/1018) seems to suggest that this is something that the user of paramiko has to implement, and gives an example of Fabric doing so.

I don't actually know how to tell that for sure; I am attaching the generated file (as .txt because otherwise GitHub can't handle it) to this post. It appears to...

I could put a `(cl:shadow)` form in the `(P ...)` form, I assume, but the point is that at runtime it _knows_ this detail, and it's not saving it. As...

(I just checked, putting `(CL:SHADOW 'PROBLEM:FIRST)` in the `(P ...)` form does fix this problem. This is a reasonable workaround for me to continue with https://github.com/orgs/Interlisp/discussions/1747.

OK, I was wrong. The above workaround does _not_ work if the package is defined and exports the shadowed symbol. That is, this crashes: ``` (P (DEFPACKAGE "PROBLEM" (:USE "LISP"...

> I am not sure whether the aim is to be compatible with CL or not. If the aim is to be compatible with CL then there are some things...

> Perhaps after being saved, this does something different. I have no idea, and I think that's the limit of what I can do to try to help I appreciate...