This is probably clojure-lsp which isn't picking up that the file has changed from ”underneath” (e.g. som git activity). What I do is that I enter a character and undo it. Then clojure-lsp refreshes its tokenization.

I'm having the same issue and was just about to ask how I can fix it.

On the repl:

I believe this is the old one I reported a few year ago

https://github.com/BetterThanTomorrow/calva/issues/849

Also there is another one https://github.com/BetterThanTomorrow/calva/issues/761

there is a workaround for that

Oh do enlighten me about that, its really annoying

It's two different bugs with similar symptoms. See here for a workaround for the two issues pasted last in this thread: https://github.com/BetterThanTomorrow/calva/issues/761#issuecomment-769960585

I see that I already have that enabled. Going through the vscode addons atm to see if theres something else trying to color the code aswell

@U02CX2V8PJN We all have this problem. The only remedy I've found is this. https://clojurians.slack.com/archives/CBE668G4R/p1668427924951079?thread_ts=1668424143.215629&cid=CBE668G4R

Ill keep that in mind and try the character adding and undoing.

You could disable semantic tokens to confirm that this is the problems. Personally I prefer the glitches over having that disabled.

Output like this:

((deftest name-test
      (testing "Context of the test assertions"
        (is (= assertion-values)))) )

I get the same. I am guessing a bug here. For workaround you can type your hotkey for Calva Paredit: Splice Sexp to remove the extra parens.

Cool, that's a new shortcut for me. Finally getting a hang of the structural editing and it is 👌

Splice is super helpful in so many cases. Good one to learn. It splices the current form contents into its parent. Or put more simply, it removes the innermost bracket/paren/quote pair surrounding the cursor.

I don’t know were this issue is, really. clojure-lsp provides that snippet. But I think it is VS Code that wraps it. Or something.

Okay, @U0ETXRFEW. I'll drop a line into #CPABC1H61 and maybe put in a bug report

Thank you!

Do we have that? Can you show a screen shot?

Is none that from Calva? Only other likely source I can think of is Error Lens, but this screenshot was taken after disabling that and restarting.

That’s from Calva’s test runner. You can run the “Test: Clear All Results” command.

Right, so I got the wrong picture in my head about ”inline”. (Which probably is the correct word for it, this was just me. 😀) Adding a screenshot to @U9A1RLFNV’s answer.

> “Test: Clear All Results” command. That's what I was looking for. 🙏

Is there a way to clear/refresh the Test Explorer? Seems to get filled up with stale entries when editing the names of tests.

It could be that Calva needs to implement some more of the API for this. I don't know, tbh. @U0K592YDP knows most about it. Unfortunately he's not working with Clojure these days, so it might be that we need to investigate this ourselves.