terminal color — the last step in a chain of decisions. A theme supplies colors; the shell and running application decide what to draw.
Why your terminal theme changes some colors, not all.
NAME
LAYERS
your shell prompt → text + color requests
your running app → text + color requests
↓
terminal emulator → resolved colors + font → screen- Emulator
- WezTerm is the application drawing the window. Its palette maps names such as “red” to actual colors. Window padding, font and transparency are separate settings.
- Shell and prompt
- A prompt decides whether to show a path, Git branch or status symbol. Changing a palette does not install those features. A missing icon often points to a missing font glyph, not a missing theme.
- Application
- A full-screen editor can supply its own theme. If it requests exact RGB values, those requests do not pass through the 16 ANSI slots you edited.
COLOR REQUESTS
ANSI slot: “draw this in red”
→ your slot 1 color
Truecolor: “draw this in #E47869”
→ that exact RGB colorTry the layers sample in the color session. Edit red: one line follows the swatch and one stays coral. This is why a good-looking palette can leave an editor unchanged.
DIAGNOSIS
The prompt changed, but the editor did not.
Check the editor’s own theme first. A program emitting truecolor can keep its exact RGB palette regardless of terminal ANSI settings. Do not keep changing the red slot to solve a color the program defines itself.
Text is readable until I select it.
Selection foreground and selection background are a separate pair. Edit them together and inspect the selected-text sample, rather than measuring only the default foreground.
My screenshot has icons; my terminal has empty squares.
Inspect the font and prompt configuration. A palette contains color values, not icon glyphs or a prompt plugin. Installing a random theme will not provide the missing character.
Technical reference: WezTerm color configuration. Original examples by HuePrompt.