One more small output view thing: vscode editor buffers have a feature where if you highlight some text, it does a light highlight on other pieces of text that match it. I often use that for quickly confirming long IDs, numbers, namespaced keywords, other long opaque values, etc. to check for errors and typos. I've been missing the ability to do that in the output view.
Cool! Please file an issue.
More multi-window weirdness with the output view. I tried to put this video in an issue but it won't let me upload it 😞 edit: I managed to compress the video enough to file an issue, hopefully it's still usable! https://github.com/BetterThanTomorrow/calva/issues/3343
Thanks for your reports. I’ve seen something similar with the total blank view with the sidebar, but only in Cursor. Hopefully the stuff you show in the video shouldn’t be too tricky to fix. Smells a little bit like a race condition to me.
VS Code clears the view when it is moved. The way we re-populate the view is that we keep the messages in memory and “replay” them. The greetings block is a bit the same, but more hard coded. So, if I just schedule things right, I think we couldn’t really fail. The total blank view could be that something crashes, so you may see something in the dev console.
Oh thanks!
I don't see any errors in the vscode devtools console when I produce the blank view
The messages I see are:
[Calva +94174976ms] output-view page loaded
[Calva +94174983ms] REPL Input mounted in output-view
It does show a few weird other messages periodically:
Unrecognized feature: 'local-network-access'.
An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.