This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-23
Channels
- # announcements (5)
- # beginners (14)
- # bigdata (1)
- # calva (13)
- # cider (10)
- # clj-kondo (53)
- # cljs-dev (1)
- # cljsrn (12)
- # clojure (67)
- # clojure-uk (8)
- # clojuredesign-podcast (3)
- # clojurescript (53)
- # duct (4)
- # emacs (1)
- # events (1)
- # figwheel-main (5)
- # fulcro (9)
- # graalvm (68)
- # graphql (3)
- # joker (3)
- # juxt (4)
- # off-topic (32)
- # other-languages (1)
- # pathom (35)
- # re-frame (6)
- # rum (1)
- # shadow-cljs (52)
- # spacemacs (3)
- # sql (10)
- # tools-deps (15)
I added the cider deps from the command in my shadow-cljs config and it seems to work well
A couple of months ago I was interviewed for The REPL podcast. It aired tonight. I think it is a pretty good listen for anyone who wants to understand the Calva project. https://overcast.fm/+OZfJpMGRI
updated the bundled VSCode clj-kondo plugin to clj-kondo v2019.11.23. this includes detection for unused imports + a couple of bugfixes.
Hey there, total VS Code and Calva n00b here. I’m trying out calva to maybe use it in a little Clojure tutorial session I’ll be giving next week. Here is my question… (I feel embarassed to ask it)… After I closed the REPL window, how do I get it back? “Open the Clojure REPL window” and “Open the ClojureScript REPL window” both give me “<command> is not enabled in the current context” messages.
Mkay, I’ve got it back by jacking in again without an alias. This opens the Clojure (JVM) REPL window. I can eval cljs forms in the editor and see the value inline. But is there a way to open the CLJS REPL, too?
Oh, okay. As soon as I actually started typing in the REPL window it switched to the cljs.user
ns after the first time I hit enter. So maybe it was running CLJS all the time, only the prompt didn’t update.
Yes, it’s an unfortunate bug of the REPL window that it doesn’t show the right cljs prompt before you have evaluated something there. We should fix that.
Dear Calva-friends: Now the PR with those Paredit changes is starting to shape up. Please help test it: https://2526-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.62-wip-editor-using-our-paredit-b108efaa.vsix Here you can read about how it is supposed to work: https://github.com/BetterThanTomorrow/calva/blob/wip/editor-using-our-paredit/docs/readthedocs/source/paredit.md