[themes] language specific tokenColors

[ghost]

"configurationDefaults: { "[language]": { "editor.tokenColorCustomizations": { … }}} does not currently seem to do anything in package.json. I think it should—please allow it.

[aeschli]

We don't support defining tokenColors by language, neither in themes nor in settings.
-> editor.tokenColorCustomizations can not be scoped by language.

Instead you have to write language specific rules as seen here: #20652 (comment)

[ghost]

We don't support defining tokenColors by language, neither in themes nor in settings.
-> editor.tokenColorCustomizations can not be scoped by language.

Instead you have to write language specific rules as seen here: #20652 (comment)

That still does not appear to work in package.json configurationDefaults. (The package in question https://marketplace.visualstudio.com/items?itemName=vomout.latex-syntax adds special syntax highlighting for certain LaTeX commands. Currently the user has to configure it instead of the package providing sane defaults. Ideally it would be based on semantic highlighting microsoft/language-server-protocol#18 latex-lsp/texlab#235 without any package—just the language server adding command-specific tags and the user configuring what they want to configure—but while waiting for that to get somewhere, TextMate regexp forest approaching SkyNet level consciousness is what we have.)

[aeschli]

configurationDefaults is only allowed for language scoped settings ({ "[language]":...`).
I created #97895 to warn about this.

I understand the desire for a grammar author (or semantic token provider) to add colors and styles for new and non-standard tokens/scopes. But its impossible to pick colors and styles that work in all themes. Theming has to be the responsibility of the theme or the user.

I don't have a good solution in mind for this right now.