[slime-devel] [RfC] (inspect foo) causing Slime Inspector to show up.

[Stelian Ionescu]

On Mon, Mar 17, 2008 at 09:10:18PM +0100, Tobias C. Rittweiler wrote:
>
>Hi,
>
>I'm working having an (INSPECT FOO) form cause the Slime Inspector to
>pop up (on those implementations that provide a way to hook into the
>their inspection machinery.)
>
>At the moment, we maintain only one *Slime Inspector* buffer, this has
>to be changed due to concurrent evaluation in several threads: For
>instance, think of code invoking INSPECT run at the REPL, and code
>invoking INSPECT evaluated in a *slime-scratch* buffer.
>
>I can think of two different schemes of maintaining inspector buffers:
>
>  a) At the moment, each `C-c I' causes an already existing inspector
>     buffer to be overwritten, change that so that each `C-c I' creates
>     a new buffer. Each invocation of INSPECT also creates a new
>     independent buffer.
>
>  b) Each `C-c I' doesn't create a new inspector buffer, but peruses the
>     one created by `C-c I' the last time (or create it.) Each
>     invocation of INSPECT creates a new independent buffer that's not
>     touched by `C-c I'
>
>Which scheme do you prefer? (Or would you rather have it entirely
>different?)

definitely a) since I often use multiple repls

-- 
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/slime-devel/attachments/20080317/4674947d/attachment.sig>