December 2008 - slime-devel - mailman3.common-lisp.net

[slime-devel] [BUG] quitting from sldb after error in thread
by Tobias C. Rittweiler 03 Dec '08

03 Dec '08

On SBCL, evaluating (swank::spawn #'(lambda () (error "FOO"))) at the REPL, then pressing `q' in SLDB results in an invocation of (FIND-RESTART NIL) which is an error in itself. -T.

1 0

[slime-devel] Reincarnate "eval..."
by Gábor Melis 02 Dec '08

02 Dec '08

Running cvs HEAD I now realize that I grew to rely on checking the modeline of lisp buffers to see whether there are outstanding requests. Often, I start evalutations that take minutes or hours to finish and it's useful to have this at a glance without having to worry about missing when the return value is printed or having to check the running threads. The attached patch does not reinstate "eval...", instead it displays the number of outstanding requests like "CON:sbcl{3}" if it's greater than zero. Currently there is a loop through buffer-list, it that's a problem maybe there is a better way to arrange for the modeline to be updated using a global mode-line-format variable as a trigger to signal the change in connection-state that is to be recomputed in each slime buffer. The patch does not solve the minor problems caused by the use of run-with-idle-timer, namely that the modeline may not be updated if the status of the connection changes in the background while emacs is idle. Cheers, Gábor

3 3

[slime-devel] slime-undefmethod contrib
by Madhu 02 Dec '08

02 Dec '08

Attached is my first contrib submission. M-x slime-undefine-function does not help when you wish to remove a specific method. This contrib adds a new function slime-undefmethod. Invoking M-x slime-undefmethod with the point inside a defmethod definition in your source will find and remove the specific method. I've posted the code before on usenet, but felt it may be more useful if packaged up with slime. Comments welcome. -- Madhu

2 1

[slime-devel] Call stack when using Lisp debugger from sldb
by Raymond Toy 01 Dec '08

01 Dec '08

Sometimes when I'm in sldb, I want to use the actual Lisp debugger because sometimes it more convenient to have a real repl. Pressing B works nicely. Previously, however, I would be in the debugger, and the backtrace would be exactly what I expected, with the top of stack being exactly where the error occurred. Now, however, the actual error is some 10-20 frames away because there are lots of slime things in between. This is kind of nice too because now I can return to sldb, which I couldn't before. But this also means I now have to go hunt around for the real offending frame. Is there a way to the old behavior? Ray

3 5