[slime-devel] Re: Slime-With-Temp-Buffer
heller at common-lisp.net
Thu Aug 7 17:10:18 UTC 2008
* Tobias C. Rittweiler [2008-08-07 17:07+0200] writes:
> 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.
OK, i changed that. For the "stale" connection problem we could
probably make the slime-connection function smarter or more
customizable. E.g. we could fall back to the current default
> 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
Will took at it.
More information about the slime-devel