Fork me on GitHub
#calva
<
2019-11-23
>
Filipe Silva00:11:42

I added the cider deps from the command in my shadow-cljs config and it seems to work well

pez10:11:50

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

borkdude16:11:16

updated the bundled VSCode clj-kondo plugin to clj-kondo v2019.11.23. this includes detection for unused imports + a couple of bugfixes.

borkdude16:11:45

btw, enjoyed the REPL interview

vinai18:11:43

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.

vinai18:11:16

Oh yeah, and I restarted vscode, jacked-in again, but that didn’t reopen the window.

vinai19:11:15

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?

vinai19:11:44

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.

pez19:11:48

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.

pez19:11:11

I hardly use the repl window, btw. Calva makes it easy to explore from the editor.

vinai20:11:02

Once I am aware of that behavior it’s no problem.

vinai20:11:17

I’m starting to enjoy working in Calva - thanks for building it :relaxed: