Jony Hudson

Hmm, that's a bit worrying. If you do manage to isolate the problem that would be super-useful :-)

Note, as this will likely involve a change to the file-format, should coordinate with #192 and #193 which both depend on persistent segment metadata.

The idea here (although it was buggy at first, and still isn't quite right) is to follow what the text REPL does, by evaluating each form in an input separately....

There's an interesting discussion over on the clojure.dev mailing list that you might have seen: https://groups.google.com/forum/#!topic/clojure-dev/Dl3Stw5iRVA It relates to a new stream-based socket REPL facility that will be built in...

I certainly agree that the current behaviour is broken, hence this issue :-) But I think the better solution is to fix the save/load of multiple outputs.

Thanks for the report @behrica :-) Have been busy these last weeks, but hopefully should have some time to put towards Gorilla shortly, and will look at this then. Jony

This is an interesting one. Originally, I was thinking that it would always be one top-level form per Gorilla segment. But then I, and others, found that it was useful...

Not sure what's going on here. I'll make some comments on the nippy issue.

That's weird. Gorilla REPL just passes on whatever the nREPL server sends to it, so I'm not sure what could be happening here. I'll take a look and see if...

There's an `op` to get a new session (`clone`). What needs cleaning up is the way that connect/disconnect happens with the websocket. It also would be good at the same...