From 47f222f66d7d481fb0d50661d64f49440455ff6d Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 24 May 2026 19:53:28 -0500 Subject: feat(keybindings): add cj/custom-keymap registration API Phase 3 of the load-graph project. cj/register-prefix-map and cj/register-command bind a prefix map or command under the C-; prefix and register the which-key label once which-key loads. Feature modules will route their registration through these instead of mutating cj/custom-keymap directly, so keybindings.el stays the sole owner of the prefix and modules stop assuming the keymap already exists at load. Adds test-init-keymap-registration.el covering prefix-map and command resolution, the optional label, and invalid-key rejection. No modules are migrated yet; that follows in batches. --- todo.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'todo.org') diff --git a/todo.org b/todo.org index a8b0e83c..9b6763aa 100644 --- a/todo.org +++ b/todo.org @@ -412,7 +412,7 @@ Do this incrementally. After each batch: - Run =make test= or at least targeted tests. - Check that keybindings still resolve and which-key labels still appear. -**** TODO [#B] Centralize custom keymap registration :refactor: +**** DOING [#B] Centralize custom keymap registration :refactor: Many modules mutate =cj/custom-keymap= or global keys at top level. This is a real architectural boundary because it forces load order and makes standalone -- cgit v1.2.3