NerdNation/OmarchyClockBar
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

README: updating needs a shell restart to take effect

Browse Source 
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) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MhxtL7WzL5XmuTd8GHbcTY
This commit is contained in:
Harvey
2026-09-04 20:18:09 +02:00
co-authored by Claude Opus 5
parent 460217d059
commit 0ef6d53e74
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+8 -1
View File
@@ -42,10 +42,17 @@ The plugin lands in `~/.config/omarchy/plugins/nerdnation.clockbar/`, and
To update it later, and to remove it: To update it later, and to remove it:
```bash ```bash
omarchy plugin update nerdnation.clockbar omarchy plugin update nerdnation.clockbar && omarchy restart shell
omarchy plugin remove nerdnation.clockbar 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` > 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` > clones disabled by default and wants you to read the code first. `--enable`
> skips that. > skips that.