Sublime Forum

In build 3126, the scope seems bugged

#1

Hi,

Since last patch, the scope seems bugged, my theme do not behave as usual.
Before (build 3114) :
3114

Now (build 3126) :
3126

The “print” was “keyword.other.python” now it’s “support.function.builtin.python”

The closed parenthesis was “punctuation.definition.group.regexp” now it’s “meta.group.regexp” and it matches the whole string, instead of just the closed parenthesis char like before.

Could you please have a look ?

Regards !

0 Likes

#2

Open a Issue on: https://github.com/sublimehq/Packages/issues

1 Like

#3

That’s right, it’s a function in Python 3, and a keyword in Python 2. You’re using Python 3 it seems, so it is scoped correctly.

Yes, scope guidelines have been updated and the default packages are being updated to follow them. You may want to update your theme rather than log an issue about a deliberate change which has been fairly well communicated IMO. (maybe not specifically that these scopes have changed, but in general)

0 Likes

#4

OK thanks,
Is there a reason open parenthesis equals punctuation.definition.group.regexp and closed parenthesis equals meta.group.regexp ?

0 Likes

#5

ah maybe that’s a bug actually, I didn’t spot it before :slightly_smiling:
the whole regex, including the parens should have meta.group.regex, but the parens themselves should also have a punctuation scope, so it seems this is missing on the closing paren. That, would be good to open an issue for :slightly_smiling: I would also vote for a separate .begin and .end scope too :wink:

1 Like

#6

Thank you :wink:

FYI, I opened 656

1 Like