Packages: no syntax highlighting for C/C++ function calls

[JaschaWetzel]

void foo() {
}

void main() {
foo(); // foo gets highlighted in 3109 but not in 3110 through 3119
}

[kleinfreund]

This is what I get with the call to foo being highlighted. Active theme is Material.

void foo() {
}

void main() {
    foo(); // foo gets highlighted in 3109 but not in 3110 through 3119
//  ^^^    source.c++ meta.function.c++ meta.block.c++ meta.function-call.c++ variable.function.c++
//     ^   source.c++ meta.function.c++ meta.block.c++ meta.function-call.c++ meta.group.c++ punctuation.section.group.begin.c++
//      ^  source.c++ meta.function.c++ meta.block.c++ meta.function-call.c++ meta.group.c++ punctuation.section.group.end.c++
//       ^ source.c++ meta.function.c++ meta.block.c++ punctuation.terminator.c++
}

[FichteFoll]

What is the active _color scheme_?

[JaschaWetzel]

Indeed it seems the LAZY color scheme is the issue.
It works with Monokai.
Several other color schemes seem to be affected as well.
I don't seem to have the Material scheme (not part of the default distro?)

[wbond]

My hope is that we can spread the word about the new Scope Naming docs to try and get various color schemes to cover what we are standardizing on.

[djspiewak]

@wbond Any hope of updating Monokai to observe the scope naming docs? It's the default theme, and a lot of people don't change it. I know several people who will complain as soon as the [Scala] changes land, despite the fact that it's mostly Monokai's fault that everything in the file is blue and italic.

[wbond]

Monokai generally does follow the guidelines, but Jon is the one who chooses what he wants Monokai to look like.

[djspiewak]

It does follow the guidelines more or less, but it has at least two too-few different colors to highlight things. The notable example of this is support.type and storage.type being styled identically, whereas several other themes (e.g. Material) style them differently, making non-C languages look enormously better. The identical coloring of entity.name.parameter, entity.name.function and entity.name.class also doesn't help.