@U2FRKM4TW How do you bypass this issue? The only thing I could do is to downgrade to v1.21.5.

That's exactly what I did. And after that, I switched the extension to NeoVim. Although can't really say right now whether it's better - I haven't been using Calva that much since then.

Are you still writing clj? Cannot imagine you are using Vscode but not with calva.

I was using Calva for a hobby project, just to get a taste of it. Now that hobby project is on hiatus, and I still use IDEA with Cursive for my main projects.

@U0ETXRFEW Thoughts on the issue? I guess all Calva+VscodeVim users are affected.

There is not anything we can do about it, afaict. NeoVIM seems to be taking another approach, letting VS Code handle insert mode. Maybe try that one?

Yup. I will try with NeoVim later.

link to the docs https://calva.io/finding-commands/

I guess this command was removed https://github.com/BetterThanTomorrow/calva/pull/344/files two years ago, so it might just be the case that nobody noticed this in the docs since then

I think you are right. It was one of @U9A1RLFNV's first contributions to Calva to make pprint a mode, iirc. It feels a bit like that would predate those docs, though, but idk.

Good catch. We should update.

I’ve updated that doc. Thanks for the heads up @U02ER5Z1KFG!

thans you both for the quick fix (and for Calva!)