4 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	9652b2d5ce	Feature 57 (config and provisioning): modules declare config and provisions, their files rendered from templates; synced with main (issues of feature 57, 874)	2026-10-16 07:37:43 +00:00
jschoubben	ca1bd18de6	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
jschoubben	73f2962bab	picom: the backend and damage tracking are each machine's settings (hq issue 345) ... A window mapped but left unpainted, or stale after a workspace switch, is a known failure of picom's glx backend with damage tracking on some drivers, and the first suspect for the empty calendar reminder on the workstation. Research 037 already found the backend to depend on the machine's driver. Both become preferences whose defaults are today's (glx, use-damage true), so nothing changes until a machine is given xrender or use-damage false to test it.	2026-10-09 12:25:08 +02:00
jochen	04894e6618	picom: the compositor as a module, claiming node-compositor (hq ADR 0208) ... Owns its configuration, moved to picom's window rules; started once from the session's xinitrc slot; Go tools restart, rules, window-opacity and toggle, which find the operator's X session from the window manager's environment.	2026-10-04 13:15:39 +02:00