Fork me on GitHub
#editors
<
2018-08-09
>
Marc O'Morain10:08:00

@pez what's your setup for editing s-expressions in vscode?

Marc O'Morain10:08:32

I've been using ClojureVSCode (I only discovered calva last week), but I'm editing parens manually.

pez12:08:55

@marc-omorain I use Calva Paredit ­čśâ And also Calva Format. My colleague adds #parinfer to the mix, but that extension hasn't received too much love lately (which might be about to change).

pez12:08:09

The reason I lifted out the formatting (indentation) to its own extension was so that it could be used together with extensions like ClojureVSCode. (Of course, if ClojureVSCode also does formatting, all bets are off. I do not know if it does, it was too long ago I tried that extension for me to remember.)

pez12:08:21

But you should now, right? ­čśâ

Marc O'Morain13:08:50

ClojureVSCode will do formatting, but only if you project has cljfmt in the dependencies

Marc O'Morain13:08:07

I've started using calva for formatting

Marc O'Morain13:08:16

I'm interested in test running

Marc O'Morain13:08:32

I added some support for the test results panel in VSCode to ClojureVSCode recently

pez15:08:19

That looks cool! I wasn't even aware there were a test results panel, or did you crate that view yourself? Calva reports test results in the Problems tab, and thus the file navigator and the files get marked up with where the tests fail, similar to how linting errors get reported.

­čĹŹ 4