Common Lisp interactive debugger

[axvr]

Hi @Olical,

I was trying out the Common Lisp support in Conjure and noticed that the SWANK client doesn't appear to support Common Lisp's interactive debugger.

Some examples in Conjure:

Same examples in SBCL command line:

You can see that no debugger info was printed to Conjure and it doesn't prompt for a debug option to be selected. (The red underline is where it prompted to select a debugger option.)

It may be that #343 is a prerequisite for this.

[russtoku]

Your issue is also related to issue #281 in the sense that direct user interaction with the Common Lisp or MIT-Scheme REPL isn't currently supported. Some hammock time is required along with some refactoring. Both clients would benefit.

A starting point may be the eval-str function in fnl/conjure/client/common-lisp/swank.fnl. The callback function passed to the send function call would need to be expanded to deal with user interaction and sending what the user types to the REPL.

conjure/fnl/conjure/client/common-lisp/swank.fnl

Line 257 in bc8907e

(fn eval-str [opts]

conjure/fnl/conjure/client/common-lisp/swank.fnl

Line 266 in bc8907e

(fn [msg] ;; handle results from Swank server

Sadly, the Common Lisp client needs someone to work on it. For some history, see #345, #348, #400, and #557.

[Olical]

Well said and thanks for linking all of these related issues together! That's helpful! A rework of how stdio clients operate so we can do more interesting things like this is high up my priority queue.