This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-12
Channels
- # aleph (11)
- # aws-lambda (1)
- # beginners (158)
- # boot (19)
- # cider (14)
- # clara (23)
- # cljs-dev (3)
- # clojars (4)
- # clojure (133)
- # clojure-dev (57)
- # clojure-dusseldorf (1)
- # clojure-finland (2)
- # clojure-gamedev (31)
- # clojure-greece (15)
- # clojure-ireland (1)
- # clojure-italy (3)
- # clojure-russia (8)
- # clojure-spec (149)
- # clojure-uk (51)
- # clojurescript (88)
- # community-development (1)
- # component (5)
- # cursive (17)
- # datomic (3)
- # emacs (6)
- # fulcro (142)
- # graphql (1)
- # juxt (15)
- # lein-figwheel (1)
- # luminus (3)
- # lumo (6)
- # off-topic (11)
- # om (8)
- # onyx (5)
- # portkey (6)
- # proton (2)
- # protorepl (3)
- # quil (6)
- # re-frame (14)
- # reagent (9)
- # shadow-cljs (226)
- # specter (11)
- # testing (96)
- # uncomplicate (5)
- # unrepl (8)
- # vim (11)
The practical issue is that repackaging cider-nrepl
into a combination of utility library, that would be useful for something like unrepl
and the built-in socket repl, plus the existing middleware is some work, that no one really wants to do. 🙂 From a technical standpoint there’s absolutely nothing hard, but someone was to implement this and also a new Elisp client library for unrepl and the necessary abstraction layer in CIDER to make it compatible with different REPL backends. All is easy, but all requires a relatively big amount of work to make it a reality.
A slightly different point of view is to use unrepl
as the abstracting layer:
• a socket repl
can be upgraded to unrepl
over the wire (CLJ only, CLJS planned)
• out of a nrepl
connection one can recreate a “pair of streams” repl (demo code in clj, you would need a bridge in elisp), once this is done, this repl can be upgraded to unrepl
And don’t forget that unrepl
doesn’t require additional dependencies on the target
so even if all you have is a serial line to the repl you can enjoy the “full unrepl experience”™