Open mrGibi opened 6 years ago
It might be a difference in oniguruma versions. That error appears to be coming from oniguruma (regex engine powering all TM grammars interpreters). I believe that SublimeText is perhaps using a different version of oniguruma or perhaps they have forked it ...
If there is no difference in scoping (and that could be hard to find) then it might be as simple as Sublime catches the exception and ignores it. I noticed some class constructs where they are using captures in the class, what if the captures didn't match? There are a lot of weird constructs in this file. Isn't [\d\D]
the same as .
? Isn't [^}\}]
the same as [^}]
?
It would help if the oniguruma exceptions would be caught and some context logged as to what patterns were being attempted, and possibly not interrupt the remaining tokenizing.
Hi, I tried importing to VS Code a syntax from Sublime's ModernPerl. Syntax is in
.plist
file, attached here: Perl.commented-bad.txt (as.txt
becouse of GitHub...). There are 3 problematic scopes in this file. They are commented out and VS Code works and colorize the Perl code, but if I uncomment them, then I get:Same file worked in Sublime perfectly. Any ideas what is causing the problem?