diff options
| -rw-r--r-- | todo.org | 10 |
1 files changed, 6 insertions, 4 deletions
@@ -698,8 +698,9 @@ Make EAT the only terminal and remove ghostel entirely (decision 2026-06-25). Ph - Phase 4 DONE (commit 6a9ec62e): retired ghostel. Migrated the terminal-generic keepers into eat-config -- the tmux copy-mode (=C-<up>= enters it, same UX + keybinding; agents run EAT over tmux so it's still tmux's own copy-mode) and the tmux-history capture, swapping =ghostel-send-string= -> a pty write and the mode checks -> eat-mode. Repointed the dashboard "Launch Terminal" to =cj/term-toggle=, swapped the =face-diagnostic= terminal-mode check to eat-mode, refreshed the auto-dim comment. Deleted =term-config.el= + its init require. EAT's default =eat-semi-char-non-bound-keys= already lets windmove / buffer-move / Emacs keys reach the terminal, so no exception-list port was needed. Tests retargeted (tmux-history 15/15). The copy-mode + tmux-history live check is a VERIFY under Manual testing and validation. - Phase 5 DONE (commit eb4aa232): removed the theme-studio ghostel app (=GHOSTEL_FACES=) now those faces are dead (ansi-color stays -- EAT inherits it), =package-delete='d the ghostel ELPA package, and swept the remaining ghostel mentions in comments/docs. The optional F8/F10 surfacing in agent buffers was not pursued. -** TODO [#C] ai-term.el commentary names a stale F9 keybinding scheme :quick:solo: -The header commentary (lines ~43-64) still documents an old =F9= / =C-F9= / =s-F9= / =M-F9= scheme for =cj/ai-term= and its family, but those bindings no longer exist — F9 is unbound in the daemon and the only live global binding is =M-SPC= -> =cj/ai-term-next= (=ai-term.el:1059=). The =M-<f9>= mention in the =cj/ai-term-shutdown= docstring (~996) is stale too. Rewrite the commentary and any stale docstrings to match the current keymap. Found 2026-06-25 while scoping the F12 -> EAT work. +** DONE [#C] ai-term.el commentary names a stale F9 keybinding scheme :quick:solo: +CLOSED: [2026-06-28 Sun] +Rewrote the header Commentary (the "four global keys" + "Four F-key entry points: F9 / C-F9 / s-F9 / M-F9" block) to the current scheme: the =C-; a= prefix map (a = toggle, s = select/launch, n = next, k = kill) plus the global =M-SPC= -> =cj/ai-term-next=. Fixed the binding-claiming docstrings (=cj/ai-term=, =cj/ai-term-pick-project=, =cj/ai-term-shutdown=, =cj/--ai-term-dispatch=) and swept the behavioral =F9= shorthand + two stray =C-F9= claims in internal docstrings. Kept the two historical incident names ("F9 shrink bug", "F9 shows another agent" bug) as recorded references. Doc-only: parens ok, no new byte-compile warnings, dispatch tests 4/4, live-reloaded. ** TODO [#B] org-capture popup leaks f12 / f10 / f11 / ai-term keys :bug: While the org-capture popup is open, the global F-keys (the =f12= term, =f10= / =f11=, the ai-term family) still fire and pop a terminal over the capture. Disable those keys for the duration of the capture popup if there's a clean way. Research first and report; if it's too invasive, defer or cancel rather than force it. From the roam inbox 2026-06-24. @@ -3810,11 +3811,12 @@ After this work lands, mark the original "Finish terminal GPG pinentry configura v1 (read-only) implemented and tested (Phases 1-3): the gkeepapi Python bridge (=scripts/google-keep/keep-bridge.py=, 12 tests), the elisp core + =cj/keep-refresh= renderer with atomic writes and async make-process (=modules/google-keep-config.el=, 15 ERT tests), un-orphaned under a =C-c k= prefix, graceful warning when gkeepapi/token/auth is missing. The pure JSON-to-org core is kept extractable per the spec. Live fetch needs the one-time gkeepapi + master-token setup — see "Google Keep v1 live setup and first fetch" under Manual testing and validation. Next: v2 (read-write — create/edit back to Keep, with a staleness guard) per the spec, the immediate follow-on once the live read is confirmed. Later: list/checkbox rendering, package extraction. Spec: [[file:docs/specs/google-keep-emacs-integration-spec.org][google-keep-emacs-integration-spec.org]] (Ready, 2 review rounds; all five decisions resolved 2026-06-25). -** TODO [#C] Remove unused system-power keybindings :refactor:quick:solo: +** DONE [#C] Remove unused system-power keybindings :refactor:quick:solo: +CLOSED: [2026-06-28 Sun] :PROPERTIES: :LAST_REVIEWED: 2026-06-20 :END: -=modules/system-commands.el= binds shutdown (=C-; ! s=), reboot (=C-; ! r=), restart-Emacs (=C-; ! e=) and friends under the =C-; != prefix. Craig rarely uses them and wants the key real-estate back. Decision resolved (Craig, 2026-06-28): remove them all — the completing-read menu still reaches the rare ones. Unbind every =C-; != key binding, leave the commands and the menu intact. From the roam inbox. +Removed the per-command leaf keys (s/r/e/l/L/E/S) under =C-; != and the prefix map. =C-; != now binds directly to =cj/system-command-menu= (the completing-read menu), via =cj/register-command=, so every command stays reachable through the menu and the leaf keys are freed. Updated the module commentary and the two keymap tests (now assert the direct-command binding + no submap; the menu-dispatch test already covers reachability). 2/2 keymap + 18/18 system-cmd tests green; live-reloaded; confirmed =C-; != resolves to =cj/system-command-menu=. Decision was Craig's (2026-06-28, cj comment): remove them all. ** CANCELLED [#C] dirvish image previews missing in the pictures dir :bug: CLOSED: [2026-06-25 Thu] |