aboutsummaryrefslogtreecommitdiffstats
path: root/AGENTS.md
diff options
context:
space:
mode:
Diffstat (limited to 'AGENTS.md')
-rw-r--r--AGENTS.md9
1 files changed, 7 insertions, 2 deletions
diff --git a/AGENTS.md b/AGENTS.md
index 329a20e..55bdf2d 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -208,7 +208,12 @@ It writes seven things: `~/.cache/udt/udt-accent.rasi` (rofi),
read through a root-made `theme.conf.user` symlink), and the accent
substitution in Sublime's installed `Packages/User/udt.sublime-color-scheme`.
It then starts `udt-homepage` and `udt-grub` detached, for the two outputs
-that need a root step on another filesystem or host.
+that need a root step on another filesystem or host, and `udt-keyboard`, which
+lights an Ajazz AK820 Pro in the accent through `ak820-ctl` (a no-op without
+it). The keyboard only listens over its USB cable, so `udt-keyboard --watch`,
+started from hypr-theme's autostart, reapplies the accent on every plug-in. Its
+firmware ignores a mode change unless the lights go off first and settle for a
+few seconds, hence the off, sleep 3, mode sequence; one second was not enough.
**Sublime's accent is replaced, not substituted into a placeholder.** Its
colour scheme cannot cascade, so the accent has to live in the one generated
@@ -252,7 +257,7 @@ those two and pywal's wallpaper-derived colours come back.
Not everything tracks the wallpaper. rofi, quickshell, Hyprland borders,
hyprlock's border (through `~/.cache/udt/hyprlock-border.conf`), Sublime's
-colour scheme and Firefox do; conky, Qt, GTK, waybar, hyprlock's panel palette
+colour scheme, Firefox and the AK820 Pro keyboard do; conky, Qt, GTK, waybar, hyprlock's panel palette
(from `templates/hyprlock/hyprlock-palette.conf`) and Sublime's UI chrome sit
on the scheme's accent, lavender by default, which is also the fallback
when a wallpaper is too grey to snap. Qt and GTK apps only reread a theme on restart,