This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-08
Channels
- # announcements (4)
- # aws (3)
- # babashka (5)
- # beginners (16)
- # cider (8)
- # clj-kondo (3)
- # clojars (8)
- # clojure (115)
- # clojure-uk (15)
- # clojurescript (18)
- # data-science (5)
- # datomic (14)
- # fulcro (49)
- # funcool (6)
- # graalvm (3)
- # graphql (4)
- # lumo (17)
- # malli (5)
- # off-topic (15)
- # reitit (18)
- # ring-swagger (8)
- # rum (2)
- # shadow-cljs (35)
- # tools-deps (18)
- # uncomplicate (2)
- # vrac (1)
@finn.volkel That’s how I do it https://nrepl.org/nrepl/0.6.0/hacking_on_nrepl.html#_interactive_hacking
https://docs.cider.mx/cider/contributing/hacking.html#_hacking_on_cider_nrepl_clojure
It’s easier for cider-nrepl, because you don’t have to restart the server and you can just keep evaluating code and you’ll get instant feedback.
@bozhidar Maybe I misunderstood you, but I was more wondering how to do it in the same repl session. So you jack-in into cider-nrepl and also point the cider-nrepl to the local copy of the nrepl and whenever something in the nrepl changes you create a new connection?