Shifts in the text selection range being detected in vscode, and given to Leo prior to executing a command.

[boltex]

As reported by @ATikhonov2 : "There is a strange thing with the command "extract", which often (but not always) happens"

Figure out how to correct the detection of the selected text range and its setup in Leo. (There is also a conversion algorithm applied in between because on one side it's just a string position, and on the other it's a row and col duo.) So there's a couple places things can go wrong!

[edreamleo]

@boltex FYI, the extract command expands the selection range to include all of the first and lines. I have no idea whether this is part of the problem for leoInteg, but Leo's behavior is necessary.

[boltex]

@edreamleo Thanks, yes I already knew this as I often use this feature to lazily select the rows I want to be extracted. (no need to carefully select from the first character of the first row needed to the last character of the last row, which is very useful)

I've been a bit busy lately but I'll start working on this tomorrow to get to the bottom of this. (selection range detection in leointeg and conversion to usable structure in leoserver.)

[boltex]

Cant reproduce precisely - might be caused by unrelated code/side-effects. Needs more details.