vscode

Quiet in here? Check #calva-dev out :smiley:
2020-01-24T05:06:31.000900Z

this seems ok so far: https://marketplace.visualstudio.com/items?itemName=CoenraadS.bracket-pair-colorizer-2 folks tried it or anything similar?

pez 2020-01-24T08:09:25.002200Z

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

2020-01-24T08:21:24.004500Z

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

pez 2020-01-24T08:24:27.005300Z

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.

👍 1
pez 2020-01-24T08:46:02.006600Z

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

pez 2020-01-24T09:47:02.007300Z

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

2020-01-24T09:50:38.009Z

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

pez 2020-01-24T09:59:11.010200Z

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...

2020-01-24T10:00:46.012300Z

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

pez 2020-01-24T10:00:54.012500Z

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.

pez 2020-01-24T10:02:02.013400Z

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

2020-01-24T10:05:47.014Z

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

pez 2020-01-24T10:31:42.014600Z

At least fewer kittens would have to die.

2020-01-24T10:48:06.015100Z

sounds like worthwhile motivation 😉