[slime-devel] Slime-With-Temp-Buffer

Tobias C. Rittweiler tcr at freebits.de
Thu Aug 7 15:07:40 UTC 2008


slime-with-temp-buffer stores a connection buffer-locally by default
even when it's not needed (*SLIME Description*, *SLIME Compiler-Notes*);
Given that those connections can become stale, I'd rather have as few
buffer store connections buffer-locally as possible, as it can result in
confusing behaviour.

Additionally, the disconnect test is subtly broken. Look into *Messages*
after running the test suite, there's "cond: Connection closed" message
resulting from the last use of (slime-inferior-process) in the test
case. The test is implicitly run in a Compiler-Notes buffer whose
connection becomes stale during the test.

And this leaves Slime in a weird state, just run the test suite a second


More information about the slime-devel mailing list