diff options
| author | Danilo M. <danix@danix.xyz> | 2026-10-19 09:29:42 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-10-19 09:29:42 +0200 |
| commit | 909b9c98da02913b603a0339cf733aa03e69897e (patch) | |
| tree | 05a5a669b330097ee262135b89a0502c597af9a4 | |
| parent | 9ffe93f709ba376fc169a8cf20c55d4ba077baea (diff) | |
| download | quickshell-909b9c98da02913b603a0339cf733aa03e69897e.tar.gz quickshell-909b9c98da02913b603a0339cf733aa03e69897e.zip | |
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 <noreply@anthropic.com>
| -rw-r--r-- | AGENTS.md | 9 |
1 files changed, 7 insertions, 2 deletions
@@ -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` |