This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-14
Channels
- # aws (1)
- # beginners (52)
- # boot (1)
- # cider (9)
- # clara (4)
- # cljs-dev (40)
- # cljsrn (2)
- # clojure (166)
- # clojure-dusseldorf (1)
- # clojure-italy (38)
- # clojure-spec (13)
- # clojure-uk (32)
- # clojurescript (337)
- # cursive (11)
- # data-science (47)
- # datomic (11)
- # emacs (3)
- # events (1)
- # fulcro (57)
- # hoplon (16)
- # jobs-discuss (1)
- # juxt (11)
- # keechma (21)
- # mount (2)
- # off-topic (44)
- # onyx (9)
- # re-frame (33)
- # reagent (1)
- # ring-swagger (3)
- # specter (2)
- # test-check (37)
- # vim (30)
Hello Colin + folks! Where can I find how to configure ClojureScript + Cursive? I tried the User Guide but could not find it
@cfleming this is something that tricks my head, why the kill sexp does a copy? I really only expect it to "kill", this is quite annoying to be honest =/
@richiardiandrea Cursive works for editing/inferring CLJS by default, what are you trying to do with CLJS? I'm not so sure about CLJS REPLs
@wilkerlucio I think this is the behaviour that paredit has on Emacs and other paredit implementations
I guess my colleagues' goal is to evaluate thing in a node repl..
not sure sorry, I haven't done much with the CLJS REPL in Cursive, but would love to do more with it
I am going to try shadow-cljs and report back
Thomas Heller has done a very good job with nRepl support it seems
@wilkerlucio @danielcompton Right, I basically copied Emacs’ behaviour here.
@richiardiandrea I’m interested in experience reports, there’s also: https://github.com/bhauman/lein-figwheel/wiki/Running-figwheel-in-a-Cursive-Clojure-REPL