debug-repl about cider

[technomancy]

I forked this off after contacting George; he said he didn't have any plans to maintain it: https://github.com/technomancy/limit-break

As is it works with a repl hooked up directly to stdin, so we need to figure out how to hook it into nrepl.

[technomancy]

In an nrepl.el buffer, evaluating *in* repeatedly gives you a new object every time:

user> *in*
#<LineNumberingPushbackReader clojure.lang.LineNumberingPushbackReader@59542b5d>
user> *in*
#<LineNumberingPushbackReader clojure.lang.LineNumberingPushbackReader@7d90f66a>
user> *in*
#<LineNumberingPushbackReader clojure.lang.LineNumberingPushbackReader@5bdeaff7>
user> *in*
#<LineNumberingPushbackReader clojure.lang.LineNumberingPushbackReader@c8e4be2>

In lein repl this returns the same one over and over. I'd guess this is why currently a breakpoint hangs; because it's expecting input on an inputstream that nrepl.el is discarded. Probably also related to the fact that *1 and friends are not being set; I would guess we aren't playing nicely with nREPL's session tracking?

[kingtim]

Yes, I do believe the sessions are getting discarded after each request. I think this is also why the interruptable-eval stuff in nREPL isn't working either. I have been looking at this and I am working on resolving this.

[kingtim]

I have version on my interrupt branch which solves the client session issue, because it was needed to be able to interrupt evaluations. Should have that committed within a day or two ... just want to do some refactoring on it. Hopefully this will help resolve the issues you outlined above.

[kingtim]

Just pushed a fix to the session related issues.

Seems to resolve the issues you mentioned above.

user> *in*
#<LineNumberingPushbackReader clojure.lang.LineNumberingPushbackReader@244c0d1a>
user> *in*
#<LineNumberingPushbackReader clojure.lang.LineNumberingPushbackReader@244c0d1a>
user> *in*
#<LineNumberingPushbackReader clojure.lang.LineNumberingPushbackReader@244c0d1a>
user> 

[dgrnbrg]

I have implemented a session-oriented repl that supports the debug repl and should be easy to integrate: https://github.com/dgrnbrg/redl

I'm still fixing up the API a bit (moving namespaces), but this supports debug-repl, nesting to arbitrary depths, sessions, and I'm working on automatic timeouts to recover from accidental infinite computations.

[technomancy]

That looks interesting, but I don't understand why a library based on providing a debug repl also contains completion functionality; it's completely unrelated.

I have a feeling that this would be better implemented entirely server-side using the discover endpoint rather than being hard-coded into the client.