Closed BlaM closed 7 years ago
Yes, that seems to be the cause. Any chance of a fix? I use this extension a lot.
Hi @BlaM , this should be fixed by latest release.
I had a workaround, which fixed #58 in the past, when an atom API function did not return correct values (bufferRangeForScopeAtPosition and bufferRangeForScopeAtCursor). This workaround did some calculation with the tabs, which obviously did not work in all cases.
Luckily, the workaround is not needed anymore, because the functions now return correct values (as far I have seen by now).
Best regards
To reproduce...
var asd = /asd(foo)/;
Now if you move the cursor into the regular expression everything is fine.
Now if you move the cursor into the regular expression it will break.
This probably causes #77.