From 909b9c98da02913b603a0339cf733aa03e69897e Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Mon, 19 Oct 2026 09:29:42 +0200 Subject: docs: a symlinked singleton needs a restart, not a forced reload Measured: after shared/Notify.qml changed, a reload triggered by editing Balloons.qml left the notifications shell on the old singleton, while a fresh instance read the new config correctly. Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index e17c65e..1c3f729 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -494,8 +494,13 @@ Hot reload does **not** follow a symlink either. Editing `shared/Notify.qml` left both running shells on the old `sanitize`, while an edit to `notifications/NotificationBalloon.qml` in the same pass did reload, so the shell looked current and was not: a remote Markdown image the new filter -blocks was fetched anyway. After editing anything under `shared/`, force a -reload of every component that links it, the same way as above. +blocks was fetched anyway. A reload forced by editing another file is not +enough either: after `shared/Notify.qml` gained `config`, an edit to +`notifications/Balloons.qml` reloaded that shell cleanly, and it kept +anchoring balloons bottom-right while a fresh `qs -p notifications` read the +same config and anchored top (compared with `hyprctl layers`). After editing +anything under `shared/`, restart every component that links it with +`./reload.sh`, from the user's terminal. Hot reload **sometimes does not fire** after an edit, with nothing logged. Twice in one session an edit was followed by no `Reloading configuration` -- cgit v1.2.3