Fork me on GitHub
#calva
<
2021-09-19
>
introom07:09:06

Dunno if anyone else here are using calva with vscodevim, however, this issue is annoying: https://github.com/VSCodeVim/Vim/issues/6992

introom07:09:40

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

p-himik08:09:05

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.

introom08:09:24

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

p-himik08:09:47

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.

thanks3 2
introom13:09:06

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

pez15:09:16

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?

introom15:09:11

Yup. I will try with NeoVim later.

andrioni17:09:29

hi, this might be a dumb question, but it seems like the sample command (eval + pprint/`calepr`) given in the docs doesn't actually exist (anymore?), could someone double-check/reproduce it? This is with Calva v2.0.211, using via remote

2
andrioni17:09:35

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

pez18:09:40

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.

pez18:09:56

Good catch. We should update.

👍 2
bringe21:09:51

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

andrioni07:09:41

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

❤️ 2