deathaxe
deathaxe
See the linked PR #3217. Unfortunatelly C/C++ reviewers are rare.
Maybe https://packagecontrol.io/packages/Wrap%20Plus can help you out.
Related with #2538
Same as https://github.com/sublimehq/Packages/pull/2308, when someone argued for breaks, hehe.
We could probably use branching to detect, whether a string is followed by `format()` and apply f-string highlighting in that case or highlight more sophisticated placeholders compared to how f-strings...
I can remember complaints about raw-strings being highlighted as regexp by default, because someone didn't want it. So either way is resulting in someone complaining because it doesn't match his/her...
We shouldn't / won't push into contexts between xml or html tags for good reasons. Matching anything outside of html tags makes any kind of interpolation by templating languages impossible....
The main reason is those to be used as base for higher level syntaxes such as ASP/JSP/PHP/... Many of them especially 3rd-party syntaxes use something like https://github.com/sublimehq/Packages/blob/4b66388fd5b206357769a9650c163f1a6958cea6/PHP/PHP.sublime-syntax#L18-L27 Push into HTML...
Are you refering to those interpolation expressions such as `$(foreach i,j,k)` ?
Bracket matching appears to depend on `punctuation.definition` and `punctuation.section`. When changing keyword.other to a punctuation scope, bracket pairs are highlighted. EDIT: It also requires `string` scopes to be cleared, which...