Calva devs (and aspiring Calva devs): I*ve updated the How to Contribute wiki page with some info on how to link PRs to issues they are addressing, and generally keep the issues updated with the work being done on them in PRs. Also added an instruction about updating the CHANGELOG.md file, which I had forgotten to mention before. https://github.com/BetterThanTomorrow/calva/wiki/How-to-Contribute#before-sending-pull-requests

I didn’t find any other reasons, but I have a question about parentheses balancing. Who is responsible for that? Paredit?

I was experimenting and even with the following settings:

"editor.autoClosingBrackets": "never",
  "calva.lintOnSave": false,
  "calva.fmt.formatAsYouType": false,
  "calva.fmt.indentation": false,
  "clojure.format.enable": false,
  "calva.fmt.newIndentEngine": false,
  "calva.fmt.removeTrailingWhitespace": false,

Calva sets them to close automatically for clojure files. Enter the "[clojure]" key in the settings file and it should autofill all Calva defaults for you.

Thanks!

Calva-devs: The repo now has a Pull Request Template, containing a checklist of the things outlined in How to Contribute. I used the template for this PR: https://github.com/BetterThanTomorrow/calva/pull/336

Dear Calva-friends: Now there is a pre-release of the next version of Calva for you to help test. It contains the following changes: * [Better inline evaluation error reports with file context](https://github.com/BetterThanTomorrow/calva/issues/329) * [Escape HTML in stdout and stderr in REPL window](https://github.com/BetterThanTomorrow/calva/issues/321) * [Adding default messaage handler for the nrepl](https://github.com/BetterThanTomorrow/calva/issues/218) * [Add command for connecting to a non-project REPL](https://github.com/BetterThanTomorrow/calva/issues/328) * [Add hover to inline result display, containing the full results](https://github.com/BetterThanTomorrow/calva/pull/336) You find the VSIX package here: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.40-release-candidate-1

Welcome, @c.fehse!

Thank you @PEZ

The last pre-release contained a horrible bug. I have removed it and now you should use this instead: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.40-release-candidate-2

Hey guys, looking to help out with simple fixes on calva as I build confidence in my clojure hacking.

That’s great, @harmmatan!

Does anyone have any especially recommended ready for vscode extension dev? I'm new to the environment and a little lost on how extension host plugs into things.

I'm taking a crack at this: https://github.com/BetterThanTomorrow/calva/issues/60 if that is helpful