Luke Gorrie luke@bluetail.com writes:
One thing I did hacking-wise is to add more significant detection of protocol errors. If the Elisp code gets a message that it can't understand in its current state, it closes the connection and pops up a buffer with some debug info and a statement to the effect of "hey, you've found a bug!". Currently I'm getting this trying to invoke the `q'uit restart in the SBCL backend, due to the Elisp :debug-condition bug mentioned above (though I'm not sure why this is hitting a debug-condition in the first place - maybe a bug in the SBCL backend).
Ack. Didn't spot this while doing the thread->unthread changes; it was trying to throw to a catch in the thread top level loop - which of course no longer exists. Now fixed.
-dan