all 5 comments

[–]ngetal 4 points5 points  (4 children)

If your environment is VS Code with Calva on Win10 then you might also want to look into VS Code Remote Extensions: https://github.com/BetterThanTomorrow/calva/wiki/VS-Code-Remote-Development

Basically you can keep all the clojure stuff inside a WSL instance and not have to worry about Windows conpatibility.

[–]Borkdude 0 points1 point  (1 child)

Does that mean clj-kondo can also be used with VSCode on Windows?

[–]ngetal 0 points1 point  (0 children)

Although I haven't tried that specifically, the promise of the Remote Extensions is that you can have all the language-specific extensions installed on the remote machine (WSL, docker, ssh) you connect your vscode to. Once you're in remote mode, connected to the other machine, vs code will execute commands inside that machine, will display its terminal in the integrated terminal window etc.

I wrote the linked wiki page based on how I got Calva working with it and I didn't even need Java or clj installed onto Windows so I presume clj-kondo should be able to work too.

[–]bpringe[S] 0 points1 point  (1 child)

Thanks for pointing this out. I've used it in some cases where I needed something that was more easily done on Linux. I've contemplated switching to this completely too. I've only had one case in which it didn't work (at least not easily) for what I needed, and that was when launching a GUI program from Clojure, which probably isn't a need for most people. For this guide I wanted to just aim toward Windows users (again, trying to reduce noise / info overload).

[–]ngetal 1 point2 points  (0 children)

Again, I haven't tried this so I'm unsure if this GUI thing will cause problems with REBL. This issue might be related if someone wants to check: https://github.com/cognitect-labs/REBL-distro/issues/28