Unclosed bracket in triple-quoted raw string breaks highlighting

[aroben]

This is basically the same as #37 except for triple-quoted raw strings.

#foo above should be highlighted as a comment. Instead, it and everything else that comes later in the file will get highlighted as if it were a regex. The grammar doesn't see that the raw string got closed at the closing triple-quote, so is happily consuming everything into the string.

The rules for triple-quoted strings use begin/end to make them work over multiple lines. We could fix the single-line case by adding near-duplicate match rules ("match": "r\"\"\"(.*)\"\"\" e.g.). But the multi-line case would still be broken:

I'm not sure how to fix the multi-line case given the way grammars currently work.

[southgate]

Highlighting gets screwy with an open parens ( too. Related?

[aroben]

Yeah almost certainly the same issue.

[pchaigno]

I'm not sure how to fix the multi-line case given the way grammars currently work.

Is it even possible? If it's not, maybe we should fix this instead of supporting regular expressions on several lines in triple-quoted strings?

[Fuzl]

Other odd behaviour breaking the block comment :

Without quotes, SELECT (uppercase only) keyword does not break block comments, but seams to trigger formating although inside block comments :

Would it be related ?

[Fuzl]

Following #109 I fetched package magicpython and deactivated language-python.
It all works correctly now.
;o)