Trying to bring some sanity back to which extension is formatting the code we have just released calva-fmt and removed some of Calva’s formatting. Calva is now dependent on calva-fmt which will get installed when you update to latest Calva. This is work in progress and you can expect calva-fmt to take care of some more of the formatting Calva is doing today. Calva Paredit will probably also start to depend on calva-fmt instead of doing its own formatting. https://marketplace.visualstudio.com/items?itemName=cospaia.calva-fmt
any idea how it plays with parinfer?
I took a break from emacs yesterday to kick the tires on VSCode again, formatting was by far and away my biggest frustration
I tried various modes of disabling calva & parinfer and couldn’t get it right
but I’ve come to realize I can’t live without parinfer anymore
calva-fmt plays nicely with Parinfer.
However, there is still a conflict to be resolved there. Calva has a feature where it tries to help place the cursor in the right position for new lines entered. We call it Auto Adjust Indent (AAI). It does not play well together with the indent mode of Parinfer. But you can easily disable AAI in Calva and let Parinfer do its magic.
We are pondering how to fix this going forward, We will try to work together with the Parinfer author to see if we can find a way for all this formatting stuff to be less of a mess. That is partly the reason why we published calva-fmt as a separate extension.
parinfer for vscode isn’t being maintained anymore tho
Officially?
https://github.com/shaunlebron/vscode-parinfer/issues/22#issuecomment-364553795
Yes, I’ve seen that, now that you remind me. Anyway, we are trying to connect and I think we should be able to find a way to maintain it. Parinfer is way to awesome to not be maintained for vscode.
I saw that in #parinfer
If I were more sold on vscode and had the time I’d be interested but I definitely do not have the time right now
Here’s hoping you will have some time later on as well as getting more sold on vscode. 😃