Fork me on GitHub
#vscode
<
2020-01-24
>
pez08:01:25

There is one built in to Calva. 😃 It is Clojure only, for good and bad.

sogaiu08:01:24

ah, much appreciated - thanks for pointing that out :)

pez08:01:27

It is Tonsky's colorizer, that he couldn't maintain any more, so now we maintain it. And we have improved on it quite a bit as well.

👍 4
pez08:01:02

Actually, I think his extension is still available on the marketplace. Clojure Warrior. It has most of my enhancements.

pez09:01:02

(In case you want to use it w/o having to bring all of Calva)

sogaiu09:01:38

tnx! i'm thinking of comparing the approaches from calva / clojure warrior with that of bracket pair colorizer 2. the latter has this interesting claim:

v2 Uses the same bracket parsing engine as VSCode, greatly increasing speed and accuracy

pez09:01:11

What could that parsing engine be? And I wonder if it means the vscode provides an API for it, or that they are just using the same tech...

sogaiu10:01:46

am curious too -- hopefully investigation will turn up some answers 🙂

pez10:01:54

I'm eager to hear about how it compares with Clojure Warrior in any case. I am considering using Calva's Clojure parser instead for it.

pez10:01:02

As it is now, Calva parses the buffer twice (actually often more than that) for structural editing and for colorizing.

sogaiu10:01:47

i guess it would be nice if that was only done once?

pez10:01:42

At least fewer kittens would have to die.

sogaiu10:01:06

sounds like worthwhile motivation 😉