Bozhidar Batsov

The problem was solved by #1910.

@sambostock Do you plan to wrap this up or should we close it?

We already have above the following rule: > Avoid chaining of `&.`. Replace with `.` and an explicit check. Perhaps it just needs to be expanded and clarified a bit...

Probably we shouldn't mention a specific number here and just expand a bit the rationale - namely that the longer the chain is, the harder it becomes to track what...

> Setting the parameters through dynvars was probably intended for end users who want to change the behavior of the printer directly from the REPL, bypassing the IDE/tooling . Do...

Let's see first what @cichli will say about this given he introduced them https://github.com/nrepl/nrepl/commit/2ddf5361bdb740cb463c4679fbafb67565a70174 I'm wondering if this ever worked in the first place. If it didn't I'd probably just...

Only @cichli can answer this. I always believed they were meant to be used in the REPL for people to experiment quickly with some settings. If that wasn't the intention...

> There is actually the (ambiguously-named and predating the print middleware) out-limit [option](https://github.com/nrepl/nrepl/blob/master/src/clojure/nrepl/middleware/interruptible_eval.clj#L93-L97) which does the same thing as buffer-size but for *out* and *err*. It's set either in an...

Is `clojure.repl.deps` something new? I remember `clojure.main/repl-requires` (that is what CIDER is using to emulate the behavior of the default Clojure REPL).

I think the proposal makes a lot of sense, although the solution is Clojure-specific as the eval for ClojureScript (in Piggieback) will still have to setup its own dynamic bindings....