piotr-semenov / parigp-lang Goto Github PK

Sublime Text (ST)

Stable Channel, Build 4169

Issue Description

When adding parigp.tmLanguage into packages directory /path/to/Sublime Text 3/Packages/User/, ST responds with error Unexpected capture value in its Developer Console.
After investigation, I discovered some undocumented requirements for ST to accept tmLanguage PLIST containing TextMate language grammar. Please, find them below as path to fix.

1. tmLanguage PLIST doesn't support nested repository tags and nested patterns for capture blocks.
2. ST uses Python regex that doesn't support variable length patterns for look-behinds.

The test below results into wrong syntax parsing.

## SYNTAX TEST "source.parigp" "Operators"

  # [1, 2, 3]
##^ source.parigp support.function.parigp

Symbol # here stands for cardinality operator, not for meta-command.

The test below results into wrong syntax parsing. Checked against VSCode 1.89.0 by its built-in scope inspector. VSIX package was built with vsce of version 2.26.1.

## SYNTAX TEST "source.parigp" "Functions"

  v = ((y, z) -> y^2 + z^2)(10);
##                        ^ source.parigp meta.function.lambda.parigp meta.parens.parigp punctuation.section.parens.end.parigp
##                         ^ source.parigp meta.function.lambda.parigp meta.parens.parigp punctuation.section.parens.begin.parigp

  \q
##^ source.parigp meta.function.lambda.parigp keyword.operator.arithmetic.parigp
## ^ source.parigp meta.function.lambda.parigp variable.parameter.function.parigp

As I discovered, if any grammar rule having begin and end keys has nested sub-rules, then it would start looking for end pattern match only after all sub-rules were applied. That's why scope meta.function.lambda.parigp doesn't end at -> as it was expected in code.

FYI, this behavior is not described at TextMate's official documentation.