Fork me on GitHub
#calva
<
2018-08-23
>
pez04:08:42

That's probably the right place to look. 😀

👍 1
pez04:08:44

But on the first question. Vscode has a built in clojure mode.

snowell13:08:36

Unsure if this is the right place to ask (it probably isn't), but I'm having a heck of a time getting auto-indenting when I hit enter to work. i.e., I type (let [v 42 and hit enter, and instead of going under the v, VSCode puts me at the beginning of the line. Applicable settings:

"calva.autoConnect": false,
    "calva.testOnSave": false,
    "calva.fmt.autoAdjustIndentOnNewLines": true,
    "calva.fmt.indentation": true,
    "[clojure]": {
      "editor.formatOnType": true,
      "editor.autoIndent": true,
      "editor.formatOnPaste": true
    }

snowell13:08:56

Format Document works fine, but my brain wants it to be right all the time!

pez14:08:04

This is the right place to ask that. And that looks like a bug. And it must be pretty recent, because that used to work!

pez14:08:49

I am currently often testing Parinfer and then need to have this auto-indenting switched off, so have missed the issue. Will investigate. Thanks for headsup!

snowell14:08:28

If it's important, I'm editing .cljs files

snowell14:08:44

And thanks!

pez15:08:20

I found the bug. When trying to prepare Calva Formatter for coexistance with Parinfer I accidently almost disabled the auto-formatting completely. I wonder how many people have been inconvenienced by this. Very, very good that you let me know. I have now released a fixed version.

pez15:08:10

Must look into how to test this kind of thing automatically. Once I figure out the mechanics it would be caught by a simple smoke test before releasing.

pez15:08:46

Check if you can already see the update (version 0.0.8). I'll be offline for a while, so really hoping it will work for you.

snowell15:08:55

It works! Thanks so much!

metal 1