Jony Hudson

I'm not actively maintaining Gorilla REPL at the moment, but @benfb is keeping things ticking over. I don't know what his priorities are, but he might be able to be...

Huh, I hadn't noticed that before. Although I'm not sure I understand exactly what triggers it. This works fine `@@ a_x b_y @@` but this doesn't `@@ a_x b_{y} @@`....

[Sorry for the slow reply - been on holiday!] Yes, this would be good. It would also be nice, perhaps, if there were to be some sort of prompt if...

Do what I think should work, but it doesn't ... may have to monitor some real nREPL traffic again to figure out what the difference is :-(

Bump out of 0.2.0.

This proves extremely difficult to debug! Send what looks like is the right message, same as what the REPLy client sends (I think) but can't get it to work. Not...

Give up on this for a second time! As far as I can tell, nREPL isn't always able to handle interrupt messages gracefully, and is sometimes left in a non-functional...

Going to close this, and will re-open if things change with nREPL's interrupt feature.

Re-open, as CIDER's interrupt seems to work just fine.

Hey @dasmoth ... haven't time to look at this yet, but just wanted to send an ACK :-) Will hopefully have a bit of time in the next few days.