Dear Calva-friends, https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.408 • https://github.com/BetterThanTomorrow/calva/issues/2382 • More Calva commands (especially related to connect and jack-in) are now awaitable @dzedasp and I have been utilizing the momentum we’ve built up on improving QOL things in Calva, especially for beginners of Calva and Clojure (Dzedas is new to Clojure and has brought me some great feedback). Todays and yesterdays changes improves the reconnect scenario in general, but is especially targeting users of the Getting Started REPL, who often have yet to realize the significance of a connected REPL. Yesterdays change helps reminding if the REPL is not connected, and todays change helps with finding the way back to which REPL type to restart and reconnect to.

I seem to be getting this behavior where .vscode/settings.json can’t have Calva connect sequences if I open a project.code-workspace file, even if the project.code-workspace file doesn’t specify that setting. Is there a way for them to be merged as opposed to ignored?

So if I want to share connect sequences among devs (checked into git) with .vscode/settings.json I could, but then I could do custom workspace things like colors etc. locally