diff options
| author | Danilo M. <danix@danix.xyz> | 2026-09-29 16:16:37 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-09-29 16:16:37 +0200 |
| commit | 8c5bdf378b8c80cc8b2fea717805c0b5fb03e070 (patch) | |
| tree | a11c80bd41019bd2b835ebde40fa5e30d4f06a32 | |
| parent | 8215c7bcde3e1fcb3635059c408b4b97e42f2141 (diff) | |
| download | quickshell-8c5bdf378b8c80cc8b2fea717805c0b5fb03e070.tar.gz quickshell-8c5bdf378b8c80cc8b2fea717805c0b5fb03e070.zip | |
An edit to shared/Notify.qml was never picked up by the running
shells, while an edit in the same pass to a component's own file did
reload, so the shell looked current and ran the old sanitize. Record
that shared/ edits need a forced reload of each linking component.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
| -rw-r--r-- | AGENTS.md | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -339,6 +339,13 @@ correct and a fresh `qs` process rendered it. Force the rescan by changing a file that imports the directory (`desktop/shell.qml`), or restart the shell. Touch alone does not reload: the content must change. +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. + `qs -p <dir>` runs one directly. `qs -p <dir> ipc call <target> <fn>` reaches a running one, which is how `SUPER+v` opens the VM drawer. |