From 0ef6d53e749492a041ad4ec67d9e62318d9c2dce Mon Sep 17 00:00:00 2001 From: Harvey Date: Fri, 4 Sep 2026 20:18:09 +0200 Subject: [PATCH] README: updating needs a shell restart to take effect omarchy plugin update pulls the new files and calls rescanPlugins, but that does not reload a keepLoaded panel plugin -- the shell keeps the QML component it compiled at startup. The files change and the bar goes on running the old build, which reads as the update having silently done nothing. Verified by writing a deliberately visible change straight into an installed plugin directory: after rescanPlugins the bar still rendered the old colour, and only omarchy restart shell picked it up. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01MhxtL7WzL5XmuTd8GHbcTY --- README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 969e47f..1f52b3e 100644 --- a/README.md +++ b/README.md @@ -42,10 +42,17 @@ The plugin lands in `~/.config/omarchy/plugins/nerdnation.clockbar/`, and To update it later, and to remove it: ```bash -omarchy plugin update nerdnation.clockbar +omarchy plugin update nerdnation.clockbar && omarchy restart shell omarchy plugin remove nerdnation.clockbar ``` +**The `omarchy restart shell` is not optional.** `omarchy plugin update` pulls +the new files and calls `rescanPlugins`, but that does not reload a +`keepLoaded` panel plugin: the shell holds the compiled QML it started with, so +the files on disk change and the bar carries on running the old build. It looks +exactly like the update silently failing. Restarting the shell is what actually +applies it. + > Plugins run as unsandboxed QML inside `omarchy-shell`, so `omarchy plugin add` > clones disabled by default and wants you to read the code first. `--enable` > skips that.