0.2.13:
start-server now binds to :: by default, and falls back to localhost,
avoiding confusion when working in environments that have both IPv4 and IPv6
networking available. (NREPL-83)0.2.11:
clojure.tools.nrepl.middleware.interruptible-eval now accepts optional
file, line, and column values in order to fix location metadata to
defined vars and functions, for more useful stack traces, navigation, etc..cljc files
containing reader conditionals has always worked transparently)0.2.10:
clojure.tools.nrepl.middleware.pr-values will not print the contents of
:value response messages if the message contains a :printed-value slot.default-executor and queue-eval in
clojure.tools.nrepl.middleware.interruptible-eval are now public.0.2.9:
clojure.tools.nrepl.middleware.interruptible-eval now defines a default
thread executor used for all evaluations (unless a different executor is
provided to the configuration of
clojure.tools.nrepl.middleware.interruptible-eval/interruptible-eval). This
should aid in the development of interrupt-capable alternative evaluation
middlewares/handlers.0.2.8:
clojure.tools.nrepl.server/start-server is
now localhost, not 0.0.0.0. As always, the bind address can be set
explicitly via a :bind keyword argument to that function. This is considered
a security bugfix, though technically it may cause breakage if anyone was
implicitly relying upon nREPL's socket server to listen on all network
interfaces.ServerSocket created as part of
clojure.tools.nrepl.server/start-server is now configured with
SO_REUSEADDR enabled; this should prevent spurious "address already in use"
when quickly bouncing apps that open an nREPL server on a fixed port, etc.
(NREPL-67)"describe" operation
via an optional :describe-fn function provided via their descriptors.
(NREPL-64):ns component of the response to "load-file" operations is now elided,
as it was (usually) incorrect (as a result of reusing interruptible-eval for
handling load-file operations) (NREPL-68)0.2.7:
interruptible-eval no longer incorrectly clobbers a session's *ns* binding
when it processes an eval message containing an ns "argument"0.2.5:
*in* with an empty :stdin value (NREPL-65):version-string is now included in response to a describe
operation (NREPL-63)java.version information in response to a
describe operation (NREPL-62)0.2.4:
*out* bindings are properly preserved
(NREPL-45)clojure.tools.nrepl.middleware.interruptible-eval/evaluate so that a
custom eval function can be provided on a per-message basis (NREPL-50)clojure.tools.nrepl.server/start-server (NREPL-51)java.version system property is now included in the response
to a describe operation (NREPL-57)*e, *1, etc) are now set in time for nREPL
middleware to access them in the case of an exception being thrown (NREPL-58)0.2.3:
*in*, to avoid intermittent failures due to
prior use of PipedReader/Writer. (NREPL-39)*print-level* and *print-length* when
generating the clojure.lang.Compiler/load expression (NREPL-41)0.2.2:
clojure.tools.nrepl/code* for pr-str'ing expressions (presumably
for later evaluation)clojure.tools.nrepl/combine-responses0.2.1:
Writer.write() and
StringBuilder.append() APIs (NREPL-38)0.2.0:
Top-to-bottom redesign
0.0.6:
Never released; initial prototype of "rich content" support that (in part) helped motivate a re-examination of the underlying protocol and design.
0.0.5:
0.0.4:
clojure.test output when clojure.test is
initially loaded within an nREPL sessionCan you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |