Dear Calva friends calva. To help the VS Code team see the huge problem with the latest Insiders version, please consider throwing your thumb up on this issue on VS Code: https://github.com/microsoft/vscode/issues/243923 π β€οΈ
Where does that [ 0, 0, 5, 10, 0 ] come from?
+ is it important that the .clj is multiline?
#_[
]
vs
#_[]
?The [ 0, 0, 5, 10, 0 ] comes from clojure-lsp. It represents one semantic token. Each token can be viewed as a five-item tuple:
1. deltaLines (from previous token)
2. charStart (on its line)
3. tokenLength
4. tokenType (10 means comment when it comes from clojure-lsp)
5. modifier bitmap
When VS Code reads this list of tokens it uses it to paint the tokens from the current theme.
The length 5, is what you get if you select the whole form, including itβs ignore marker (and newline, could be that it is length 6 on DOS machines). So far I have only seen the freeze problem happen with multi-line tokens.
Came here to check for a bug and this is exactly the issue I am having. Except I have downgraded Code-insiders and Calva already. Any tips for versions to have a work-around? Ps. upvoted the issue.
Nvm, I see 1.99 is the culprit in the issue, reverting to 1.98
@thierry572 if you download the VSIX found here https://app.circleci.com/pipelines/github/BetterThanTomorrow/calva/8582/workflows/f3977360-7536-405e-b32a-6a3dc3669457/jobs/47696/artifacts and install in VS Code 1.99 it should avoid this issue. I need some more testing on it, and you can help. π
I also get a lot of these, but might be unrelated
I can do that, let me shut down my repl
need to reinstall newest vscode too
VS Code Insiders, right? I hope it hasnβt reach the regular VS Code yet.
yes I use insiders
installing now
Dunno if Calva related, but these weren't there in 1.98 and previous Calva version
bunch of aggregate errors
no dissapearing text uet
yet*
still going strong
many FAILED event errors, but its still woprking
Bunch of these too
Yeah. We should clean up the errors. But they have been there for years, so unrelated.
Unfortunately not fixed with latest Calva and vscode
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.492
β’ https://github.com/BetterThanTomorrow/calva/issues/2679
With flares we can trigger behaviour in VS Code from the REPL (any Calva connected REPL). This release ships with the first flare: #flare/html{β¦}, which lets you open a WebView using HTML or any URL. Read more about flares here: https://calva.io/flares/
Thanks, @timothypratley for adding this! β€οΈ π calva
That is sick! it would be super cool if you could somehow get a hold of a html element - then you could render your reagent stuff in the repl π€―
(tagged-literal 'flare/html {:html (rdom/render [:h1 "foo"] <???element???>), :title "Greeting"
:key "example"})
Recently, @timothypratley and @pez collaborated on the new Flares feature, that allows opening the VSCode WebView as a result of a REPL evaluation. https://calva.io/flares/ https://github.com/BetterThanTomorrow/calva/pull/2680 Yesterday, @timothypratley used that and updated the https://scicloj.github.io/clay/#setup of the Clay tool. So now, with Clay, rendered forms and namespaces will open automatically inside the vscode webview. We will discuss this feature briefly in a couple of upcoming meetings (today and Monday): https://clojureverse.org/t/clojure-real-world-data-28/ https://clojureverse.org/t/visual-tools-meeting-31-workflow-demos-5/
π€―
Some help with testing this VSIX would be greatly appreciated. β€οΈ calva π