Shen Tian

Had to think for a moment what the `partial` flag would do, but it sounds like it would allow the client to detect that it's receiving streamed messages (or not),...

Separate question I picked up on: Existing docs say: > Note well that the printing function is expected to not interact with *out* or *err* at all, even rebinding them...

> > This approach respects that by placing the weight of config file values quite high up, between 1) and 2), rather than between 3 and 4, which I originally...

Just to add some notes (from clojurians) to this issue: lein can do this through a custom middleware when it starts a server: https://github.com/technomancy/leiningen/blob/145ba54eb0a5fc099380ad6feb04688a2fca9173/src/leiningen/repl.clj#L147-L167 but this is not relevant when...

Thinking about what the client-side change would need to be. Having a look at the source for lein now... looks like the change would need to happen there and in...

Is your expected behaviour that `*ns*` should be `dev.scratch` in the last response? Looking at what docs are around, it is a bit ambiguous what `:ns` in response means, but...

> ... and that always used to work correctly. Would be handy if you can check in which version this behaviour changed?

@cursive-ide : any luck reproducing this?

Sorry, deleted that message there because I realised it was missing the point.

But as far as I can tell the return `:ns` value is just there so the client knows, during the course of the eval, *ns* was changed, so it can...