🎅

vscode’s locked down API is a blessing and a curse. I think mostly a blessing.

For your dotfiles, @mattly, maybe you can script something using the --list-extensions arg to the code command?

About linting: If Calva is set to lint on save it will also lint on open, as @mseddon figured out, maybe that should be changed, or the setting renamed. The Joker extension is unrelated to Calva, but both use Joker. They will probably both add problem records to the same errors. So keeping Calva’s lint-on-save on while using that extension is not recommended.

If that extension is actively maintained, then we should maybe consider dropping Calva’s linting?

Calva could also bundle that extension.

The Calva linting also needs a way to clear the problem pane: https://github.com/orgs/BetterThanTomorrow/projects/1#card-16017001

Ah that explains why I’m seeing the same error twice for the first error

decided to just bash through my extensions syncing dilemma: https://github.com/mattly/dotfiles/blob/master/bin/codex