Fork me on GitHub
#calva
<
2022-08-31
>
pez09:08:33

Dear Calva-friends. Yet another release: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.298https://github.com/BetterThanTomorrow/calva/issues/1848 See the previous ^ message for details on this change.

thomas09:08:47

silly question.... but does Calva automatically update?

thomas09:08:18

or do I need to press a button somewhere. I guess this is a VS code thing, not calva specific of course

pez09:08:29

I think it might be an option in VS Code. I also think that by default VS Code keeps extensions updated. When a new Calva is installed while a VS Code window is open, the VS Code window will need to be reloaded to use the new Calva. The extension pane will show you if it has extensions that are updated, but need a VS Code window reload.

👍 1
pez09:08:59

Note that a VS Code window reload is not the same as a VS Code restart. Each window has its own extension host,

pez09:08:32

Also note that if you start the REPL manually in a VS Code integrated terminal and then connect to this REPL (instead of Jack-in), then VS Code will persist the terminal session between reloads and reattach. Then you only need to reconnect the REPL. This way a VS Code window reload can be a very minor interruption of your work.

👏 1