Clojurians Log v2

Seems odd. An issue would help us dig in more.

There is always time to learn Emacs later. Personally i have no desire to go back to Emacs. It felt like I had to battle with it all the time, whereas Vscode is working together with me. I don't even use a VIM extension, that's how modern I've become. 😎

I don't know about aliases, but maybe an alias is not always needed?

Is there a way to stop evaluation, when it takes too long or is in an endless loop? I can kill the jvm task, but that seems a bit too much?

There is an Interrupt Running Evaluations command for that. Depending on the nature of the hang, it might not work, but most often it does, is my experience.

Thanks, I'll try this

Yes, that’s weird, I noticed that lag a few days ago. I re-installed Calva, but it didn’t help. Also I tried one before the change, and the lag was still there for some reason. Finally, I tested it on my work machine, there was no lag (the latest version).

Dear Calva friends. I apologise in advance for any inconvenience brought by the Calva version just released: v2.0.139. It has a workaround for an issue with lsp on Windows. But that is not what I think might cause inconveniences. That comes in with a change to Calva jack-in where we move away from abusing the VS Code Task system to a solution where we use the Pseudo Terminal APi to control the jack-in process. This has been very long in the works and I have never dared release it. But I am out of ideas on what might break now and it doesn’t seem people are very interested in testing the VSIX-es I’ve put out (probably because it is quite unclear what it is about). So, now, with hopes that it shouldn’t break things, but fears that it might, it is released. Please be quick to test that jack-in still works for you as it used to.

Might be something with VS Code then… What version are you using on your work machine?

Local Version: 1.52.1 Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523 Date: 2020-12-16T16:30:02.420Z (1 wk ago) Electron: 9.3.5 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: 8.3.110.13-electron.0 OS: Darwin x64 19.6.0

So that’s the same as I am using.

Work Version: 1.51.1 Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f Date: 2020-11-11T01:11:34.018Z (1 mo ago) Electron: 9.3.3 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: 8.3.110.13-electron.0 OS: Darwin x64 19.6.0

OK. So it figures with the timeline that this started to happen with 1.52.

Probably, I downgraded to 1.51.1 and it didn’t help.

Weirdness

If I turn my wifi off, the lag disappears.

Oh, wow.

Indeed, Same here.

With that wifi clue I found that bumping to latest cider-nrepl for jack-in fixes the issue.

Since ^ v2.0.140 is out, with a fix for the strange delay with which evaluation error messages where delivered.