Fork me on GitHub
#calva
<
2023-08-10
>
pez13:08:04

Dear Calva friends. When updating Calva’s dependency on cljfmt I discovered that our reliance of an internal/private function in there bit me hard. I had to rework things quite significantly to make things work again. Now I have a version of Calva using cljfmt 0.11.2, and things seem to work. Please help me test it a bit more. Here’s a VSIX you can take for a spin: https://output.circle-artifacts.com/output/job/aec0c5dd-df3d-4050-abb7-82d3525942dd/artifacts/0/tmp/artifacts/calva-2.0.383-2274-cljfmt-0-11-2-878be858.vsix To do so, download it and then install it from the context menu of the VS Code Extensions pane (Install from VSIX…). Thanks in advance! 🙏 ❤️ calva

👌 2
chromalchemy22:08:09

Is there a way to use 1 semicolon for comments instead of 2? I don’t really care that much for future use, but I’m using a codebase I developed in Cursive, and there it was set to 1. So my existing comments are not recognized for toggle comment on/off actions.

pez06:08:49

I don’t think there is.

pez21:08:35

You are welcome to file an issue about it. Iirc this toggle is implemented by VS Code, from a language configuration that is static, so to make it possible to toggle comments of some other type we would have to roll our own implementation. I.e. not a super quick fix, but also not very big, I think.

chromalchemy00:08:29

Ok, thanks for context. It’s not critical, I can probably do a simple find/replace, but just checking if I was missing something.