Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.493 • https://github.com/BetterThanTomorrow/calva/issues/2757 Latest clojure-lsp adds semantic tokens for ignored (`#_`) forms. This disables the syntax highlighting of these forms. This release of Calva filters the comment tokens away, restoring Calva’s highlighting of ignored forms. It also seems to avoid the bug in VS Code insiders which messes up rendering of files with ignored forms something awful. Good in case that bugs slips out to the stable VS Code builds.
I still have the dissapearing text issue with this version 😞
With latest insiders build and latest Calva
Going to roll back again
Are you sure you’re actually have latest Calva active?
Calva is utilizing cider-nrepl and clojure-lsp to create this VS Code experience.
nREPL dependencies configured:
nrepl: 1.3.1
cider-nrepl: 0.52.1
cider/piggieback: 0.6.0
clojure-lsp version configured: latest
If you are new to Calva, please see:
And please consider the command: **Calva: Create a Getting Started REPL project**
Calva version used: v2.0.494
vscode:
Version: 1.99.0-insider
Commit: 299b150bd5c0227099c9b03dc56c5073ec0ff5e2
Date: 2025-03-24T05:03:53.092Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Linux x64 6.11.0-19-genericThanks. Can you repro it with this simple text?
#_[
]will need to jack-in again, this happens directlly after jack-in, hold on 🙂
Jack-in just shouldn’t matter…
It's probably because of the app that starts logging into the repl window
Ah, so then I am super curious about what could be in there.
And you can maybe avoid the issue by using the terminal as output.
just text about starting modules
I will try that, was super happy I could use the repl window again as I cant get used to repl output not showing eval directly at my cursor
You can keep evals there.
My cursor is just never there. Lol.
my cursor is in other files too, lol. I read the output from the repl window
moved everything back into the terminal window for now
will see if i can repro
the logging of the app startup ends with a sequence filled with namespaces like so:
#'aorta.module.zorgdomein.endpoints/service
#'aorta.service.import/service
#'aorta.service.import-xml/service)other then those lines there are no hash characters in the logging lines
A reason we don’t recommend using the REPL window for stdout and stderr is that it often contains unstructured text that can throw things out of whack, since it is a Clojure file. But for evaluation results it should be fine. (Minus VS Code Insiders shenanigans). That output has an unbalanced paren, for instance.
after moving everything into terminal it seems okay
I had it like so:
"evalResults": "repl-window",
"evalOutput": "repl-window",
"otherOutput": "terminal"
and now have it like so:
"evalResults": "terminal",
"evalOutput": "terminal",
"otherOutput": "terminal"It may not be about the hash characters at all. So far it has all been about some clojure-lsp provided semantic token spanning more than one line. But this could be a different beast, because I don’t think clojure-lsp is even active in the REPL window… I could remember that incorrectly.
So evalOutput is typically stdout. FYI. evalResults is structured output since it is Clojure data.
I have these in my lsp config.edn
:source-paths-ignore-regex
["aorta-develop\/dev.*"
"aorta-develop\/resources.*"
"aorta-develop\/test.*"
"\/home\/thierry\/\.m2\/repository.*"
"\/home\/loud\/\.m2\/repository.*"]
:paths-ignore-regex
["^\.calva.*"
"^\.clj-kondo.*"
"\.joyride.*"
"^build.*"
"^\.lsp.*"
"^\.portal.*"
"^target.*"
"^dev.*"
"^resources.*"
"^test.*"
"\/home\/thierry\/Documents\/\.docs-code.*"
"\/home\/loud\/Development\/\.docs-code.*"]Yeah, so even if the repl window should be handled by clojure-lsp you seem to exclude it there.
yes
I can copy the logging output to the repl and see what happesn, hold on
If you can share output with me in DM, I can try isolate.
nothing happens, no dissapearing stuff
sure
It needs to be when there is dissapearing stuff for you. 😃
Could of course be tricky to copy invisible text, but it could work with select-all, then copy.
lol, now its not dissappearing. need to restart vscode
Worst kind of bug!
Set my replwindow settings back to repl output but no dissapearing stuff
argh
okay, what I will do is copy my repl window output when the text dissappears and send it to you in a dm
right
it broke lol
going to save the file
Awesome. 😃
and copy the contents
Is there a command to specifically send something to the repl window when every output is set to terminal?
I can repro with that text. Haven’t isolated yet, but these obervations: • It doesn’t happen if I open the file while it is outside the project. • It happens immediately if I paste it in the Calva REPL Window • It happens only with clojure-lsp active. (If I stop clojure-lsp the file immediately renders again).
good to hear you can repro it atleastr
I can’t reliably repro, though. So it will take a little while to minimize. 😃
Right, now it also happened with everything set to terminal and aftger I pasted a copied inspector item to the repl window
i will send it to you in DM
Dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.494 • Fix: https://github.com/BetterThanTomorrow/calva/issues/2759 I hope this should restore the way auto-connect sequences without projectRootPath worked before. @seancorfield Can you confirm that your sequences as they were before you added projectRootPath to them work as before?
Yup, I removed the projectRootPath setting, confirmed it was broken in my current Calva, updated Calva and reloaded the window and it auto-connected without error. Tried several other scenarios with the new Calva version and they all seemed to work.
So is ["."] the default now for projectRootPath?
Thanks! 🙏 I also tried combos I could think of, but it is an explosion.
At first I thought I should fix it with a default. Then I realized we actually need to restore the old behavior, which is to prompt for the project root when it is not specified, and there is more than one candidate.
Ah, that makes sense. It's why I have it in the auto-jack-in config (but not in the auto-connect config) as I recall!