Fork me on GitHub
#chlorine-clover
<
2021-08-18
>
seancorfield05:08:52

After seeing @pez setup Gitpod for Calva for his Rich4Clojure repo, I wondered what would be involved in getting Clover working in Gitpod... https://github.com/seancorfield/deps-new starts up VS Code with Calva and Clover installed, with a modified config.cljs file in place (copied from the .clover folder in deps-new), starts a Socket REPL (on port 50505, puts that in .socket-repl-port so Clover can find it. I haven't figured out how to persist keybindings in a repo, but Gitpod seems to persist those itself (I'm assuming it uses your GitHub sign-in to somehow sync that across workspaces?).

pez06:08:09

Very cool!

mauricio.szabo17:08:25

Yes, I was testing GitPod on some of my projects too, it was working until I found out that there are some APIs they didn't yet support. Seems that's fixed now, then? 🙂

pez17:08:32

Yes, it is by default using VS Code now, and they are phasing out Theia.

mauricio.szabo14:08:46

BTW, I forgot to tell: I think Clover already works with Gitpod, right? Let me check on my test project and I'll update here

mauricio.szabo15:08:46

Yes, it does work, even with custom commands:

pez16:08:17

Yes, I think Clover even worked when Gitpod was using Theia. Which is extra cool in my book.

seancorfield16:08:33

Yeah, all my repos are setup with Calva + Clover + Socket REPL and the setup copies in my custom commands, and I have my key map configured as well.

seancorfield16:08:08

With the custom commands for Clover you have to copy the config file in at startup which took a couple of goes to get right (because the Clover config folder doesn't exist at that point). Right now I have that config file in each of my repos. e.g., https://github.com/seancorfield/next-jdbc/blob/develop/.clover/config.cljs

seancorfield05:08:27

(just added that to clj-new, depstar, honeysql, and next-jdbc as well)