feat(terminal): themed Kitty when OpenGL < 4.3 (#95)
All checks were successful
Check / eval (push) Successful in 3m41s

Ghostty needs OpenGL 4.3; older GPUs (Intel HD 4000) top out at 4.2.
Installer probes glxinfo and writes settings.terminal=kitty into
theme-state when below the floor. modules/home/kitty.nix enables Kitty
with the same palette, mono font, and opacity as Ghostty so the fallback
still looks like Nomarchy.

Default machines stay Ghostty-only (no kitty in the HM closure). Doctor
and calendar still invoke Ghostty by class — V3 on Acer for SUPER+Return.

Verified: V0 flake check; installer-safety; HM with terminal=kitty builds
themed kitty.conf + TERMINAL=kitty; default template has no kitty bin.
This commit is contained in:
2026-07-15 09:45:32 +01:00
parent a09399702d
commit 1e648b6c49
12 changed files with 179 additions and 71 deletions

View File

@@ -436,12 +436,12 @@ the **T14s** (webcam case).
**without** running `home-manager switch` by hand. **Fail** = still
need the recovery one-liner, or GTK/nm-applet still wrong until a
manual switch (then the bake is still incomplete).
- [ ] **#95 Ghostty on Acer M5-481T only** — XPS is fine (clarified
2026-07-15). On the Acer after the fix: SUPER+Return opens a usable
terminal without hand-adding kitty. Today both attempts fail: (1)
pre-HM → explicit `OpenGL 4.2` / `OpenGLOutdated`; (2) post-HM →
quiet exit after `GDK_DISABLE=gles-api,vulkan`. Confirm post-fix
both lifecycle points open a window. Modern-GL default remains Ghostty.
- [ ] **#95 themed Kitty fallback on Acer M5-481T** — after install from an
ISO that probes GL &lt; 4.3 (or set `settings.terminal = "kitty"` +
`nomarchy-home`): SUPER+Return opens **Kitty** with Boreal (or current
theme) colors/font — not unthemed stock. `theme-state.json` should
show `"terminal": "kitty"`. Ghostty may still refuse if launched by
name (expected on HD 4000). XPS / modern-GL machines keep Ghostty.
- [ ] **#124 flake pin after main-ISO install** — on a machine installed
from a **main-built** ISO (post-fix): `~/.nomarchy/flake.nix`
nomarchy input must not re-resolve to a lagging `v1` that lacks