Open the keybindings menu on first login

The welcome toast spent three lines telling you about a cheatsheet that takes
one keystroke to read, and the only way to act on it was to click the toast,
which opened that cheatsheet. Open it directly instead.

Dismissing the menu exits non-zero, since no selection was made, so the step
tolerates that rather than failing first run and retrying the whole sequence
next login.

It also goes last now. The menu blocks until it is answered, and the Wi-Fi and
update toasts are the only other things left to show, so sending those first
leaves them waiting underneath rather than behind an open menu.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
David Heinemeier Hansson
2026-08-11 11:56:03 +02:00
co-authored by Claude Opus 5
parent 383addc8c4
commit 23d85a992b
4 changed files with 12 additions and 10 deletions
+4 -3
View File
@@ -237,9 +237,10 @@ systemd instance:
- `install/user/first-run/gnome-theme.sh`,
`install/user/first-run/gtk-primary-paste.sh` — GNOME/GTK settings that
need the dconf daemon.
- `install/user/first-run/welcome.sh`,
`install/user/first-run/wifi.sh` — welcome and Wi-Fi/update toasts
(waits for a live notification server before firing).
- `install/user/first-run/wifi.sh` — Wi-Fi/update toasts (waits for a live
notification server before firing).
- `install/user/first-run/keybindings.sh` — opens the keybindings menu to
greet the first login; blocks until it is answered.
The entire sequence has one idempotency marker:
`~/.local/state/omarchy/done/first-run-user`, managed by `omarchy-done`.