found-issue — found while implementing #7.
Problem
Existing machines have:
~/.config/omacase/login-items -> $OMACASE_ROOT/home/dot_config/omacase/login-items
PR #29 moves that tracked file to config/omacase/login-items. The moment the user pulls that commit, the live symlink dangles. OmacaseLauncher reads the user path at login; until _launcher_seed_login_items runs (omacase wm / omacase install), OmniWM (and anything else in the file) will not launch at login.
#29's seed helper does fall back to the new seed when the dest is gone, so a later install is safe. The gap is the window between git pull and the next launcher install.
Why it matters
Login-time window manager startup is the most user-visible path. A dangling symlink is a silent miss, not an error.
Suggested fix
- Run the seed helper from
omacase doctor and/or the omacase entry point, not only _launcher_install.
- Or add a tiny one-shot migration that converts the link on first
omacase update after the destage, before anything else.
found-issue — found while implementing #7.
Problem
Existing machines have:
PR #29 moves that tracked file to
config/omacase/login-items. The moment the user pulls that commit, the live symlink dangles. OmacaseLauncher reads the user path at login; until_launcher_seed_login_itemsruns (omacase wm/omacase install), OmniWM (and anything else in the file) will not launch at login.#29's seed helper does fall back to the new seed when the dest is gone, so a later install is safe. The gap is the window between
git pulland the next launcher install.Why it matters
Login-time window manager startup is the most user-visible path. A dangling symlink is a silent miss, not an error.
Suggested fix
omacase doctorand/or theomacaseentry point, not only_launcher_install.omacase updateafter the destage, before anything else.