This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-19
Channels
- # aws-lambda (1)
- # beginners (35)
- # cider (7)
- # cljsjs (2)
- # clojure (48)
- # clojure-austria (1)
- # clojure-conj (9)
- # clojure-dev (8)
- # clojure-india (6)
- # clojure-italy (12)
- # clojure-nl (8)
- # clojure-norway (3)
- # clojure-spec (9)
- # clojure-uk (92)
- # clojurescript (103)
- # community-development (7)
- # cursive (15)
- # datomic (75)
- # devcards (3)
- # emacs (3)
- # events (1)
- # fulcro (129)
- # hoplon (4)
- # immutant (2)
- # jobs (10)
- # leiningen (9)
- # off-topic (4)
- # onyx (2)
- # re-frame (45)
- # reagent (39)
- # reitit (40)
- # remote-jobs (4)
- # ring (2)
- # ring-swagger (9)
- # shadow-cljs (17)
- # tools-deps (31)
Is the "no response handler with id nil" something that only occurs with quil?
I haven't seen it elsewhere but working with quil is almost unusable because of it
@theeternalpulse Pretty much yes. If you search in the issue tracker you’lll see some workarounds.
I'm moving on to Clojure2d for now, is this something that you think has to be fixed in quil?
For some reason some reason with it there are some nREPL responses generated without a matching request id and this confuses CIDER. I never had time to investigate this, though I have some ideas how to potentially handle this.