Restart the shell unconditionally after every update
Updates routinely replace the shell's QML, and a stale process can lazy-load new files into old code. Restarting at the end of every omarchy update removes the need for migrations to restart the shell or defer one with the restart-shell-required marker: the login-time migration path already runs a fresh shell that hot-reloads shell.json. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
72ffd58316
commit
c992cdff10
@@ -127,6 +127,9 @@ New migration format:
|
||||
- Use helper commands such as `omarchy-cmd-present`, `omarchy-cmd-missing`,
|
||||
`omarchy-pkg-add`, `omarchy-pkg-drop`, `omarchy-pkg-present`, and
|
||||
`omarchy-pkg-missing` when appropriate.
|
||||
- Never restart the Omarchy shell. `omarchy update` restarts it unconditionally
|
||||
after migrations run, and the login-time shell already runs current code and
|
||||
hot-reloads `shell.json` edits.
|
||||
|
||||
Example:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user