Highlighting support.class scope (example on PlantUML language)

[The-Lum]

Hello,

We have some questions about language highlighting.

---

Discussion inspired from:

• Github C4-PlantUML syntax highlighting  qjebbs/vscode-plantuml#428

For example, if we take the PlantUML language with the corresponding syntax definition:

• https://github.com/qjebbs/vscode-plantuml
• https://github.com/qjebbs/vscode-plantuml/blob/a151047641c224772d6553d98ccfe1b60483c60a/syntaxes/plantuml.yaml-tmLanguage#L202

---

• Why the support.class.preprocessings.source.wsd keywords are not highlighting on Github?
  while very well on VS Code...

See keyword !include on this simple example:

@startuml
!include filename.puml
@enduml

• How to differentiate explicitly the textmate scope support.class on Github?
• Where is the issue?

Regards.

[lildude]

• Why the support.class.preprocessings.source.wsd keywords are not highlighting on Github?

Well they technically are (they're not black/white depending on dark mode) but only because GitHub only implements limited support for support keywords with support.class not being one of them.

@Alhadis maintains a great list showing the supported keywords and their colours in https://github.com/Alhadis/language-etc/blob/master/samples/lists/scope-previews.nanorc

Also see his comment at #4568 (comment) for more details on how GitHub behaves.

[The-Lum]

Thanks a lot.

Your other answer on #5204 (comment) is also helpful.

Then, I will look on the theme side (to ask if a explicit differentiation is plan) or on the initial language grammar (in order to change the scope of the preprocessing keywords).

[Alhadis]

I see this part of my comment was accurate:

Don't get too attached to the colours you see. […] Expect the exact colours to shift over time.

… because today I noticed that GitHub's variable colour has changed from #E36209 to #953800. 😉