thanks, i will go that route. the only downside is that it highlights everything in red until i configure clj-kondo but that's pretty minor.

How does it behave if you disable Calva?

Ah good call - I’ll check

I don't see a change in color of the require letters (#2) in that gif. Am I missing something? Regarding #1, @U0ETXRFEW Is that a side effect of color-matching the open/close characters? Wonder if there is a way to prevent the highlight. I am differentiating here between coloring (which we call highlighting some in the code base I think), and actual highlighting like when you select text with the cursor.

If you see the u and i in require start off blue when I type them, then go to orange (the final stage).

@U0ETXRFEW with calva disabled both issues disappear (but I get VSCode paren match which is weird, though better looking visually IMO)

Thanks for trying that out. Calva‘s matching is quite involved, a lot of things happen when one character is typed. But maybe we can control the rendering some. Please file an issue.

I will - was just curious if this only happens to me

I haven’t noticed, and haven’t tried yet, now that I know what to look for. But I really doubt it is just on your machine.

My machine is from 2014 but generally everything still ticks along 😅

Made an issue so I don’t forget: https://github.com/BetterThanTomorrow/calva/issues/673

Thanks!