-
Notifications
You must be signed in to change notification settings - Fork 154
New scope name for preprocessors #197
Comments
My votes are, in order of preference;
|
I'm working on maintaining the TextMate grammar for VS Code, so I'd like to coordinate this naming change with you all just to keep theming for both VS Code and Atom somewhat in sync. I agree there isn't going to be a perfect fix. For most themes I think it is just going to end up being colored with the default color for My vote preference would be for one of
Why
|
Not including prerequisites as they don't apply.
In #188, there was some discussion that
entity.name.function.preprocessor.c
was not correct. Some alternatives that were proposed, as well as some that I'm proposing right now:entity.name.macro.preprocessor.c
entity.name.identifier.preprocessor.c
entity.name.expression.preprocessor.c
entity.name.preprocessor.c
entity.name.macro.c
None are widely supported by themes, and also have no precedent.
Textmate docs are here, though they don't cover this as well. Proposed Atom naming conventions also doesn't cover this.
cc: @thomasjo @alpyre @simurai @MaximSokolov
The text was updated successfully, but these errors were encountered: