Skip to content

Applying themes

Run generation for the selected theme before applying it. Selection reads generated source files; it does not synthesize a target configuration on demand. Confirm the theme ID and generated path in the integration catalogue.

Adapters can decline application through their environment gate. A desktop target may be unavailable in Termux, and a Termux target may be unavailable on desktop. A skip is not proof that the generated source is missing.

Selection applies adapters sequentially. A failure does not undo earlier successful applications, and a partially successful operation can persist last-used state. Read every reported target result, inspect the live destination for successful targets, then correct the failing target and retry.

A configuration is not changing as expected

Section titled “A configuration is not changing as expected”

Some integrations use fixed configuration imports, copied sources, package files, or generated pointers rather than editing the most obvious live file. Follow the source and destination paths listed for that adapter instead of hand-editing a file that the next apply will replace.

Reload hooks are best-effort and target-specific. Verify the live destination first, then restart or reload the application manually if its hook is unavailable or fails. Refer to the target’s catalogue entry for documented reload behavior.