mesh-catalog

Files

T

jschoubben ca1bd18de6

mesh/merge-gate pass: builds picom → g14, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)

Details

mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Details

mesh/delivery superseded: a newer delivery to the same trunk took over its walk

Details

picom: keep the configuration trusted, so only the terminal sets the backend (review of #157 )

A setting is pasted into picom.conf as it is, so a backend of xrender"; write-pid-path = "… adds an
option of the caller's: picom would then overwrite any file the operator can write. With the file
trusted, both settings are set at the controller's terminal alone until settings are typed and quoted
(hq issue 346).

2026-10-09 12:33:41 +02:00

args.go

picom: the compositor as a module, claiming node-compositor (hq ADR 0208)

2026-10-04 13:15:39 +02:00

main.go

picom: the compositor as a module, claiming node-compositor (hq ADR 0208)

2026-10-04 13:15:39 +02:00

manifest_helpers_test.go

picom: the backend and damage tracking are each machine's settings (hq issue 345)

2026-10-09 12:25:08 +02:00

manifest_test.go

picom: keep the configuration trusted, so only the terminal sets the backend (review of #157 )