This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-16
Channels
- # announcements (2)
- # asami (124)
- # babashka (30)
- # babashka-sci-dev (73)
- # beginners (40)
- # biff (1)
- # calva (39)
- # clj-kondo (54)
- # clj-otel (1)
- # cljdoc (59)
- # cljs-dev (8)
- # clojars (2)
- # clojure (96)
- # clojure-austin (16)
- # clojure-boston (6)
- # clojure-europe (51)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-russia (60)
- # clojure-uk (4)
- # clojurescript (34)
- # community-development (6)
- # cursive (2)
- # datahike (10)
- # datascript (18)
- # emacs (109)
- # etaoin (1)
- # events (3)
- # figwheel-main (41)
- # fulcro (13)
- # helix (4)
- # introduce-yourself (5)
- # jobs (1)
- # leiningen (5)
- # lsp (8)
- # malli (6)
- # meander (7)
- # nrepl (6)
- # off-topic (60)
- # pathom (29)
- # polylith (8)
- # re-frame (5)
- # reitit (1)
- # releases (1)
- # remote-jobs (1)
- # rewrite-clj (33)
- # sci (3)
- # shadow-cljs (3)
- # xtdb (82)
Well, if you started the server process from a REPL it'd be pretty easy to figure out it's host/port. 🙂
Thanks! 🙂 My use case was being able to add a middleware at runtime, from a function call at the runtime itself (rather than from CIDER/Calva). This way, libraries would be able to add middleware without needing any editor-specific setup. (Does it make sense to desire that?) (Anyway, for me this use case is on hold at the moment. In the thread above, I decided to rely on other methods to listen to user evaluations, for now -- just to avoid the setup details that caused some confusion. I'm hoping to explore the nREPL middeware option again in the future.)
@daslu Why do you need to extract those from the runtime? After all that's usually static type of information that's known at connection time.