Fork me on GitHub
#chlorine-clover
<
2020-10-29
>
mauricio.szabo17:10:25

Ok, so... I was looking at VSCode API for Clover, and I believe I have good news. It's possible to register "tasks", and they can be registered dynamically. Also, you can register keybindings to tasks. so this means that the newer version of Clover will be able to be almost as configurable as Chlorine!

đź‘Ť 1
seancorfield17:10:15

Nice! So the whole cljs config thing from Chlorine could be ported over to Clover/VS Code?

mauricio.szabo17:10:35

Yes, exactly! It's possible that it can be literally copy-pasted, without needing to adapt code between versions

mauricio.szabo17:10:45

This means that it's dotfiles friendly too

seancorfield17:10:03

If all my customizations for Atom/Chlorine can work on VS Code/Clover, I would probably switch to VS Code 🙂

seancorfield17:10:49

I'm happy to do early testing if/when you think Clover is ready -- will it have the same "editor" API that Chlorine has?

mauricio.szabo17:10:15

Yes, that's the idea. In fact, I believe that the editor API is already working, I just need to wire some callbacks to VSCode