Hi,
Is it possible to call slime's inspector from CL? This would come handy when I want to inspect a variable inside a function. If I call (inspect my-variable), I get SBCL's inspector, which is not nearly as nice as SLIME's.
Currently, I work around this by saving the variable (eg (defparameter *my-variable* my-variable)) and inspect it after the function is finished, but doing it directly would be nicer.
Thanks,
Tamas
Is it possible to call slime's inspector from CL? This would come handy when I want to inspect a variable inside a function. If I call (inspect my-variable), I get SBCL's inspector, which is not nearly as nice as SLIME's.
see break/inspect and friends in here:
http://dwim.hu/darcsweb/darcsweb.cgi?r=HEAD%20hu.dwim.debug;a=headblob;f=/so...
hth,
In article hu7mvb$q1v$1@dough.gmane.org, Tamas K Papp tkpapp@gmail.com wrote:
Hi,
Is it possible to call slime's inspector from CL? This would come handy when I want to inspect a variable inside a function. If I call (inspect my-variable), I get SBCL's inspector, which is not nearly as nice as SLIME's.
Currently, I work around this by saving the variable (eg (defparameter *my-variable* my-variable)) and inspect it after the function is finished, but doing it directly would be nicer.
Thanks,
Tamas
SWANK:INSPECT-IN-EMACS. The :WAIT parameter determines whether the function call should be waiting for you to close the inspector buffer.
Non-waiting would be especially nice with the ability of having multiple inspectors open at the same time which is not currently possible. I've wanted to implement that for the last two years (and started at some point but never finished it.)
It's not hard. Maybe the next time I find myself annoyed by that shortcoming.
-T.
On Jun 3, 2010, at 4:43 AM, Tobias C Rittweiler wrote:
Non-waiting would be especially nice with the ability of having multiple inspectors open at the same time which is not currently possible. I've wanted to implement that for the last two years (and started at some point but never finished it.)
Being able to have multiple inspectors open would be beneficial. I understand this involves a departure from the nested approach of the current inspector. I hope you find time to get back working on it, and will be glad to test and provide feedback on the swank server side of the implementation (used by MCLIDE).
-- Terje