If anyone is testing the new version of the vscode extension that is brewing, together with Calva, this is important for a smooth experience: https://github.com/BetterThanTomorrow/calva-fmt#parinfer-and-auto-adjust-cursor-on-new-lines

Also, to save some time for people who want to test the bleeding edge version of Parinfer for vscode, install this VSIX package: https://clojurians.slack.com/files/U0ETXRFEW/FC8D62QGZ/vscode-parinfer-0.6.3-pez-testar.vsix

Let me know if this should be posted as an issue instead (thinking it might not belong there as I am testing a yet unreleased version). Anyway, is this behaviour by design?

(def a [:b |↩︎:c])

(def a [:b]) 
|:c

(def a [:b 
        |:c])

(Using smart mode)

@pez The same done in Atom produces

(def a [:b 
        :c])

Good! 😃

@pez The source of ground truth for figuring out if a bug is yours or in parinfer itself is https://shaunlebron.github.io/parinfer/demo

If it works there and your version is broken, it’s your bug 🙂

If it’s broken over there then it’s a parinfer bug.