calva 2026-11-03

EDIT: This is strictly about the output destinations, output-view, and output-sidebar. I am finding that as output grows large, VS Code starts to get sluggish. The syntax highlighting makes us create a lot of DOM nodes, and the views have pretty large retention windows. Anyway, until I’ve fixed, you can clear the windows if you experience any slowdown of VS Code. Should give you the performance back. https://github.com/BetterThanTomorrow/calva/issues/3336

I've been deleting repl output for ages already, every day a couple of times 😎

👍 1

You should’ve said something 😃

😅 I just assumed it's a "feature"

I also mangle data a lot, so it really grows

But good to know it isn’t a completely new problem that I have introduced with my latest spree of output view things. Even though I may have made things worse.

Checking. Which output destinations do you use?

Would output-channel have that problem too? I've started to notice lags, but chalked it up to my work computer being low-specs.

I recently switched from terminal to output-channel as my main output (and it might very well be the case still, just checking).

I don’t think the output-channel has this problems. Those are used by many extensions and VS Code itself for tons of output designed by the VS Code engineering team.

Ok thank you. Computer dying is a very probable cause then laughcry

If the output view is one of your outputs, that’s a suspect. It doesn’t need to be the main output.

No, I have removed it for now.

> Checking. Which output destinations do you use? That one was for you, @jussi.mononen

"calva.outputDestinations": {

        "evalResults": "repl-window",
        "evalOutput": "terminal",
        "otherOutput": "terminal"
    },

Ah, so that’s not was this issue is about. The repl-window is a regular file mostly and it will start to get sluggish at some point. You can continue regarding that as a feature. I see it as a bad choice of output destination. 😃

👍🏻 1

😂 pebkac then it is

When I have a fix for the output view perfoemance problems I am pretty sure they will be a much better choice for you.

🙏🏻 1

Could we just have an option to turn syntax highlighting off? Would that alone "fix" the problem? (I'm not saying don't fix the root cause, just an option for those who don't care enough about the highlighting to put up with any slowdown)

Worst case maybe. But to my experience there is no such thing as “just an option”.

I'm guessing the "real" solution is to virtualize off-screen parts of the page, and that's what the vscode team does to make large files performant?

Seems to be a VS Code issue. But we should be able to work around it mostly, I think.

Here’s a build that adds some settings for controlling how much lag you allow. • old now: https://app.circleci.com/pipelines/gh/BetterThanTomorrow/calva/10407/details?useNewPipelines=true&workflowId=60789d26-e9c9-4a5e-a1b6-af67fd8f1700&job=24cc392d-a6a3-45f1-98b4-8c2098c25c35&buildNumber=66503&jobType=build&tab=artifacts . • https://output.circle-artifacts.com/output/job/c5251167-20de-4dd9-bed0-c9f0ebd1ac27/artifacts/0/tmp/artifacts/calva-2.0.610-3336-output-views-light-d51ab12e.vsix Search settings for outputViews to get a picture, I will need to add documentation. @chromalchemy, you use screen readers? If so would be super helpful with your feedback on this build. With the outputViews screen reader support off, I see zero lag/stutter with this build.