This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-30
Channels
- # adventofcode (3)
- # announcements (4)
- # babashka (42)
- # beginners (56)
- # biff (23)
- # cider (8)
- # clj-yaml (2)
- # cljdoc (16)
- # clojure (83)
- # clojure-europe (52)
- # clojure-nl (3)
- # clojure-norway (4)
- # clojure-sweden (2)
- # clojure-uk (2)
- # clojurebridge (1)
- # clojurescript (2)
- # cloverage (1)
- # cursive (11)
- # data-oriented-programming (1)
- # deps-new (2)
- # dev-tooling (2)
- # emacs (3)
- # etaoin (4)
- # events (5)
- # fulcro (5)
- # gratitude (3)
- # java (3)
- # jobs (1)
- # jobs-discuss (1)
- # joyride (33)
- # malli (16)
- # music (1)
- # nbb (1)
- # nrepl (4)
- # nyc (1)
- # off-topic (25)
- # pathom (8)
- # re-frame (1)
- # reitit (7)
- # remote-jobs (2)
- # shadow-cljs (6)
- # tools-deps (9)
Can nREPL servers send unsolicited messages back to clients? Example, a nREPL server could insert a tap> sink, and forward tapped data to the nREPL client (e.g. an editor)
I'm pretty sure that's how printing works. The server listens to stdout/stderr and forwards those to the nrepl client for the editor to print.
this happens because nrepl provides a “subscribe-out” operation which closes over the transport (i think). I don’t think there’s an easy way to ad-hoc send things back without changing some code in nrepl
It's been a while since I've looked at this, but I think something like the following should work: • create a middleware that requires the eval middleware • idempotently add a tap that will send a message to the client