This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-23
Channels
- # aleph (1)
- # architecture (4)
- # aws (7)
- # beginners (249)
- # boot (17)
- # calva (4)
- # cider (30)
- # cljdoc (7)
- # cljs-dev (1)
- # cljs-experience (3)
- # clojure (69)
- # clojure-dev (7)
- # clojure-europe (1)
- # clojure-italy (7)
- # clojure-japan (15)
- # clojure-spec (6)
- # clojure-uk (39)
- # clojurescript (51)
- # cursive (31)
- # data-science (4)
- # datavis (1)
- # datomic (40)
- # dirac (67)
- # duct (8)
- # editors (15)
- # emacs (9)
- # events (3)
- # figwheel-main (2)
- # fulcro (157)
- # juxt (4)
- # kaocha (11)
- # lein-figwheel (1)
- # off-topic (31)
- # pathom (18)
- # re-frame (4)
- # reagent (2)
- # reitit (16)
- # remote-jobs (1)
- # shadow-cljs (11)
- # specter (2)
- # speculative (1)
- # tools-deps (27)
- # vim (1)
- # yada (2)
I have dabbled with it a few times, yes.
(on both Mac and Windows)
@kyselyradek which extension are you trying with? If it is Calva, we can try help out in #calva-dev .
Cool! And you now know where to look for help. We in the Calva team are committed to provide a productive Clojure experience for VS Code users. It does have rough edges still, but we are at it!
Should I uninstall the default Clojure
extension before adding Calva
or should it support both?
I don’t know how default that extension is, even if it has a very apt name. 😃 But yes, disable or uninstall it. Calva is not compatible with it.
Yes, use Calva — I don’t think the Clojure extension is maintained any more (I never bothered even trying it).
Oh, looks like it was updated as recently as early December. My bad.
There’s a #vscode channel if you still want to ask about the Clojure extension there but I’ve had no problems with Calva — for the little that I use VSCode (I went back to Atom and I’m now using Chlorine with that).