Multi-language colors and custom schemes

Identify the active scheme#

Choose the full Andromeda variant in Appearance, then confirm Editor → Color Scheme. A custom scheme selected earlier can continue to govern source while the tool windows follow the new theme.

Find the specific category#

Duplicate the supplied scheme. Open the affected language’s colors and inspect the token category. HTML attributes, CSS values, Python function names, and Java classes need not inherit the same general identifier color.

Semantic highlighting provided by a language plugin can be more specific than the base lexer category. If changing a generic text color has no effect, inspect the language-specific settings rather than repeatedly modifying unrelated attributes.

Test a realistic file#

Use comments, strings, numbers, types, and expressions, then add selection, search highlights, and a completion popup. Check diagnostic underlines against both the normal background and selection. A custom color needs to work in those states as well as ordinary source.

Keep typography deliberate#

Change family, size, and line spacing under Editor → Font or an explicit scheme override. Hold those values fixed when comparing Andromeda, Aurora, Solar, Forest, and Nebula.

Recover and report#

Select the supplied matching scheme to restore code colors and reapply the theme for UI resources. If another appearance provider changes icons or panels, compare with one provider active.

Include exact variant, scheme, language/plugin, and token/state in a report. A small source example plus a screenshot of the selected state makes the affected category much easier to identify.