hl-valdemar/tinty-wrapper
1
0
Fork 0
Code Issues Pull Requests Actions Packages Releases Wiki Activity

docs: use TOML for Conjure configuration

Browse Source
This commit is contained in:
hl-valdemar
2026-10-22 15:51:40 +02:00
parent c60890eb4a
commit 586e1c75e7
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -4
View File
@@ -123,13 +123,13 @@ Configure OMP to use `tinty-current` where required.
The `apply-apps` flow writes `$XDG_CONFIG_HOME/conjure/theme.json`, falling back to `~/.config/conjure/theme.json` when `XDG_CONFIG_HOME` is unset, empty, or relative. The generated JSON contains seven opaque colors: `background`, `text`, `secondaryText`, `accent`, `glow`, `keyBackground`, and `error`, using Tinty semantic UI colors with Base16/Base24 or tinted8 palette fallbacks.
Opt in by adding this to `conjure/config.json` in the same configuration directory:
Opt in by adding this to `conjure/config.toml` in the same configuration directory:
```json
{"theme":"tint"}
```toml
theme = "tint"
```
The wrapper never changes `config.json`. Optional entries in its `colors` object override generated colors. Conjure reads configuration only at launch: restart Conjure after applying a theme or editing its configuration. The wrapper does not signal, reload, restart, or notify Conjure.
The wrapper never changes `config.toml`. Optional entries in its `[colors]` table override generated colors. Only the machine-generated `theme.json` uses JSON; edit the TOML configuration instead. Conjure reads configuration only at launch: restart Conjure after applying a theme or editing its configuration. The wrapper does not signal, reload, restart, or notify Conjure.
## Usage