Clojurians Log v2

@pez hi, i have free time to try again VSC 🙂 Just I am curious. Why did you start Calva when https://github.com/avli/clojureVSCode exist? (I didn’t try it)

For me you win, because you have better doc. It gives much better impression you care about it.

I’m glad to hear. The idea is that Calva should be actively maintained. ClojureVSCode seems to serve many people well, but it didn’t have the Emacsy/Ciderish interactive coding that I wanted, and I had some problems getting it to work in an intuitive (for me) way with mixed Clojure/ClojureScript projects. The alternative that worked best for me was VisualClojure, but things stopped to work after a major update and the author just left it there. My PRs were never even commented, so I decided to fork off from there.

So the best config for now is to install: https://github.com/shaunlebron/vscode-parinfer https://github.com/PEZ/paredit-for-vscode add

"parinfer.defaultMode": "disabled",
    "calva.autoAdjustIndent": true,

Did you figure out solution for spaces between keys and values in maps?

I am a little confuse what parse code now… Parfiner extension? Calva?

both?

> However Parinfer clashes with the auto adjustment of indents feature. Can you explain it a little more? indent mode looks ok as first impression. Better than calva.autoAdjustIndent.

I didn’t code anything real for now, but it looks Parinfer needs some extra configuration like aligment for map and should be fine

ok with this settings it looks like terrible things happening… ok there is something wrong

so the best is to use calva.atuoAdjustIndent true and parinfer.defaultMode Paren?

not sure what calva.autoAdjustIndent does

it is still confuse for me, sorry

Calva’s adjustment help is all about getting the cursor at the right place when creating a new line. It kicks in using an onTypeFormattingProvider in vscode. Parinfer does its work on the selection changed event. Sometimes Calva wins, sometimes Parinfer.

I intend to do something about all this. Thining of building a formatter extension with an API that Calva and Paredit and other extensions can use. In the best of world’s this formatter would be doing all Clojure formatting and the other extensions can concentrate on their main use cases.

I just need the days to be much longer, and I would make it. 😃

So the vision is to make formatting in Calva and not use Parinfer?

Maybe one day I will learn Type Script and contribute to Clojure community… but not today 🙂

At least I have to learn Type Script in my current work, so… maybe in a few months

Calva is being rewritten in clojurescript, just sayin’. :face_with_cowboy_hat:

The idea is to do formatting in a clojure formatting extension, and keep using parinfer for inferring parens.

BTW I found cmd+z doesn’t work because of formatting. Especially when paste some block of code.

hmm we will see if this combine parinfer and Calva formating wouldn’t bring some issues. I am a little afraid of that.

For now it is still not productive environment for me, because of issues about editing code.

But I am excited about it, looks promising