Struct EnvView 

pub struct EnvView {
    pub is_stdout_tty: bool,
    pub no_color: bool,
    pub term: Option<String>,
    pub colorterm: Option<String>,
    pub force_ascii: bool,
    pub force_unicode: bool,
    pub lang: Option<String>,
    pub lc_all: Option<String>,
    pub is_windows: bool,
    pub wt_session: Option<String>,
    pub term_program: Option<String>,
}

All environment signals we care about for rendering decisions.

Default returns the safest non-TTY-ish snapshot (no special env vars, no UTF-8 hint, not Windows). Tests use it via ..Default::default() so adding a new field doesn’t require touching every fixture; production code goes through EnvView::probe.

Fields

is_stdout_tty: bool

no_color: bool

term: Option<String>

colorterm: Option<String>

force_ascii: bool

Set when the user has explicitly asked for ASCII-only rendering (e.g. ATOMCODE_ASCII=1). Escape hatch for terminals whose font can’t render our Unicode prompt glyphs (❯, ◆, etc.) and would otherwise show □ tofu.

force_unicode: bool

Set when the user has explicitly opted INTO Unicode rendering (ATOMCODE_UNICODE=1) — overrides the Windows-legacy-console auto-fallback for users who installed a font that does have the glyphs (Cascadia Code, JetBrains Mono, etc.) on plain conhost.

lang: Option<String>

lc_all: Option<String>

is_windows: bool

true when running on Windows. Affects the default-Unicode decision because the legacy conhost host pairs with fonts (Consolas, NSimSun, …) that don’t include ◐, ❯, etc.

wt_session: Option<String>

WT_SESSION — set by Windows Terminal. Strong signal that the terminal has a modern font with broad Unicode coverage.

term_program: Option<String>

TERM_PROGRAM — set by VS Code, iTerm2, WezTerm, Hyper, etc. Any value here means the user is on a modern emulator that almost certainly ships a Unicode-capable default font.

Implementations

impl EnvView

pub fn probe() -> Self

Trait Implementations

impl Default for EnvView

fn default() -> EnvView

Returns the “default value” for a type.