Emilio Jesús Gallego Arias

Thanks a lot for the report @LasseBlaauwbroek , this is a jsCoq-specific problem. We use a different position method (as we support some editors like ProseMirror), and indeed, that method...

That's fanstastic, thanks for the feedback! We have indeed done a lot of not very rewarding work trying to make the setup easier. I can see the STM problems you...

I don't mind at all, but keep in mind that if interrupts are broken in JS, checking large files will be annoying. > How do I do that? With the...

Thanks to you for the feedback, now that we have users of the new jsCoq 2.0 branch we'll try to fix these issues ASAP.

Hi @KevOrr , likely our documentation is out of date, we are a bit short on dev power. We have a template here, that one I think works pretty well,...

Very nice, I assume you have tested these changes? I'll ping @corwin-of-amber as he's the main expert on worker creation / CORS, but otherwise things look good to me. Likely...

Thanks a lot folks, this seems good to me. How can we test this is working properly? Is there a way to a npm pre-release or something? A couple of...

> @ejgallego Do you know of a trick that allows merging these changes into both branches? In Coq we have a bot keeping track of that, but for us I'm...

See https://github.com/coq-community/vscoq/issues/670 for screenshots (tho the second screenshot doesn't reflect how it should print either I think)

That's the correct rendering: