This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-11
Channels
- # aleph (38)
- # announcements (6)
- # aws (1)
- # beginners (47)
- # calva (21)
- # cider (47)
- # cljs-dev (18)
- # clojure (40)
- # clojure-europe (7)
- # clojure-india (2)
- # clojure-italy (9)
- # clojure-nl (11)
- # clojure-norway (2)
- # clojure-sanfrancisco (1)
- # clojure-spec (17)
- # clojure-sweden (2)
- # clojure-uk (73)
- # clojurescript (10)
- # cursive (6)
- # datascript (12)
- # datavis (2)
- # defnpodcast (1)
- # duct (5)
- # emacs (36)
- # figwheel (2)
- # figwheel-main (10)
- # juxt (12)
- # leiningen (1)
- # midje (1)
- # nrepl (9)
- # off-topic (25)
- # pedestal (3)
- # portkey (3)
- # quil (2)
- # re-frame (45)
- # reagent (1)
- # ring (3)
- # ring-swagger (36)
- # rum (1)
- # shadow-cljs (48)
- # spacemacs (1)
- # speculative (50)
- # testing (2)
- # tools-deps (27)
- # yada (4)
@jeremy642 To my knowledge Cursive should work just fine with the modern nREPL.
@bozhidar Cursive still uses the old one, but IIRC it should be compatible with the new server, right?
I’ll upgrade the nREPL Cursive uses for the next release, but that will only be for REPLs managed by Cursive - ones started via lein will use whatever version Lein uses.
@cfleming It’s compatible on the protocol level, but the middleware is not compatible because of the namespace change.
Generally it’s a bad idea to mix them in the same project as some middlewares use conditional requires to figure out which one to load and if some other code loads the unexpected nREPL you get into a situation like Jeremy’s.