Closed jonnay closed 14 years ago
This precise error is fixed in the networking branch (in the master branch, you currently need to write "null-process"). The more general error of "unbound variable" bouncing you into the lisp debugger is the piece of issue #2 that still remains to be completed (being able to use x
instead of 'x
).
The null-process
-> null
conversion has been merged with master in 2d15ca722fa2b23bbdcb1aa2d9eae55ab4a5b5ab.
Closing this, as the reported error has been fixed.
This is with running the network branch version of client-server.kiln on the 0.3 executable
Running it produces this
After that, the kilns binary doesn't accept any input. typing in (state) or (:y 2) does nothing.