diff options
| -rw-r--r-- | todo.org | 22 |
1 files changed, 15 insertions, 7 deletions
@@ -787,7 +787,10 @@ What we're verifying: the physical keychord opens a floating Dirvish popup; open - Expected: GUI nautilus opens (the binding nautilus moved to) *** Network module Phase 1 — indicator states on the live bar What we're verifying: =custom/net= shows the right state for each real network condition. The engine logic is unit-tested; this is the live-bar + visual check (states can't be faked on the running bar). Phase 2-3 tests get added under this task as those phases land. -- Reload waybar to pick up =custom/net= (Super+B, or =pkill waybar; waybar &=). +- Reload waybar to pick up =custom/net=. Super+B does NOT reload a running bar — it only toggles visibility (SIGUSR1), and the bar reads a generated runtime config, so a stale copy keeps the old module. The correct reload regenerates the runtime config then restarts: +#+begin_src sh :results output +waybar-active-config && killall waybar && waybar-toggle +#+end_src - On a normal connected network, read the module. - Expected: wifi glyph + signal + SSID; tooltip shows IPv4, gateway, throughput, and a recent "online" probe result. - Join the hotel/captive network (or any portal network). @@ -805,12 +808,17 @@ rfkill list wifi # confirm Soft blocked: yes make -C ~/.dotfiles online # or: net doctor --fix #+end_src - Expected: doctor reports the rfkill block, runs =rfkill unblock wifi= + =nmcli radio wifi on=, reconnects, and ends "online" — all from the TTY. -*** Network module Phase 1 — airplane state absorbed, display-only (option 1) -What we're verifying: =custom/net= shows the airplane state, the toggle stays the airplane-mode low-power script (now on the net module's right-click), and only the redundant *display* pieces were removed. Craig's call: net absorbs the display, not the low-power orchestration. -- Right-click =custom/net= (it now runs =airplane-mode=). -- Expected: airplane engages — wifi drops, brightness dims, CPU/services to low-power — and =custom/net= shows the airplane glyph in gold. Right-click again restores everything. -- Check the bar has no separate =custom/airplane= module, and =waybar-airplane= / =waybar-netspeed= are gone from =~/.local/bin= (dangling symlinks removed). -- Expected: no duplicate airplane indicator; =airplane-mode= itself is still present (=ls ~/.local/bin/airplane-mode= → exists), since the low-power toggle is not a network concern. +*** Network module Phase 1 — bar clicks + airplane keybind +What we're verifying: the custom/net clicks do the useful thing and airplane is a deliberate keybind, not a misclickable foot-gun (it disconnects you). Clicks (revised after live use 2026-06-29): left = =net doctor --notify= (desktop notification, no terminal — diagnose is read-only), middle = nmtui scratchpad, right = =net portal= in a floating terminal (=net-popup=, so the sudo prompt + browser work). Airplane = Super+Shift+A. The sudo fix path (=net doctor --fix=) stays =make online= in a terminal. +- Left-click =custom/net= while online. +- Expected: a desktop notification "Network / Online" (success), nothing changed. When offline it notifies the problem + next action. +- Right-click =custom/net= on a captive network (or at a hotel). +- Expected: =net portal= runs in the floating terminal — reset + opens the portal page to log in. +- Middle-click =custom/net=. +- Expected: the nmtui scratchpad (manual connection manager). +- Press Super+Shift+A. +- Expected: airplane engages (wifi off, dim, low-power); =custom/net= shows the airplane glyph in gold. Super+Shift+A again restores everything. +- Check =airplane-mode= is still present (=ls ~/.local/bin/airplane-mode=), and =waybar-airplane= / =waybar-netspeed= / =custom/airplane= are gone. ** DOING [#B] Prepare for GitHub open-source release :PROPERTIES: |