This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-29
Channels
- # announcements (1)
- # babashka (120)
- # beginners (184)
- # cider (14)
- # clara (2)
- # clj-kondo (25)
- # cljfx (9)
- # cljsrn (43)
- # clojure (46)
- # clojure-australia (2)
- # clojure-berlin (5)
- # clojure-dev (2)
- # clojure-europe (10)
- # clojure-france (3)
- # clojure-nl (1)
- # clojure-spec (14)
- # clojure-uk (30)
- # clojurescript (50)
- # code-reviews (19)
- # conjure (11)
- # core-logic (2)
- # cursive (20)
- # datascript (1)
- # datomic (74)
- # figwheel-main (1)
- # fulcro (10)
- # funcool (2)
- # graphql (1)
- # lambdaisland (1)
- # malli (2)
- # meander (22)
- # nrepl (13)
- # off-topic (28)
- # overtone (3)
- # pathom (7)
- # pedestal (4)
- # re-frame (4)
- # reagent (16)
- # reitit (4)
- # releases (1)
- # ring (8)
- # shadow-cljs (93)
- # specter (6)
- # sql (13)
- # test-check (1)
- # tools-deps (1)
- # tree-sitter (2)
- # vim (8)
- # xtdb (25)
No, it's not. Each REPL is backed by a single connection. It shouldn't very hard to hack around this - e.g. start two connections in the same project and change the evaluation dispatch code to send the forms to all connections of the same type in the same project. But it's probably going to be a big ugly. 🙂
The use case is I have an app spun up twice but I'd like to keep the backend code in sync
No comment syntax is defined. Use: Does anyone get this error occasionally in emacs when using cider?
Possibly related? https://github.com/clojure-emacs/cider/issues/2724
sorry, I don't see the connection. Are you sure you referenced the correct issue?
ahhh. I see.
I suspect it is somehow related to the fact that I pressed 'm' in the cider-macroexpansion buffer, and my macro intentionally threw an exception.