Romain Tetley
Romain Tetley
This is a duplicate of #877. I am busy working on a fix ! I will keep open because of the ```L is declared``` thing. This is probably related to...
This is fixed in v2.2.4
 I don't see this. Which version of vscode do you have ?
Nothing was changed on my side.
How large a file are we talking ? Even the infamous ```Pff.v``` which is almost 30 000 lines long takes about 2 to 3 seconds to parse on my setup....
I think this could somewhat be linked to #1048. It seems there is some sort of race condition in the parsing of the file which ends up having an incorrect...
So we compute the lsp range using the Loc.t from Coq via: https://github.com/coq/vscoq/blob/96b677a32d43dfd9ce7aa2a9f1ac7480477b0f2e/language-server/dm/rawDocument.ml#L83C1-L87C4 Looking at the code we seem to use ```loc.bp``` and ```loc.ep``` from the type: ``` type t...
What is the status on this @gares ?
@gares what is the status on this ? Will you have time to work on it before the next planned release (around the first week of February) ?
Thanks a lot for your report. In the above when you describe issues with the positioning of breaks in the ```Pp_cmd``` themselves I am pretty sure this is a Coq...