|
|
@@ -339,6 +339,7 @@ This phase aims to create a robust, extensible, and performant keybinding system
|
|
|
* Move all existing C++ fallback implementations (e.g., `core_->move_up()`, `core_->buffer().insert_char()`, `core_->buffer().erase_char()`) from `TuiEditor` and `GtkEditor` into distinct, named commands registered with the new `CommandSystem`.
|
|
|
* Bind these new commands to their default key sequences (e.g., "ArrowUp", "Backspace", "Return", "a") within the `KeyBindingManager` (likely in default C++ configuration or via `init.lua`).
|
|
|
* The UI frontends should then *only* call `core_->lua_api()->process_key(key_name)` (which will then delegate to `KeyBindingManager` and `CommandSystem`) for all key presses.
|
|
|
+ * **Status Update:** Completed. C++ fallback keybindings have been eliminated from both `TuiEditor` and `GtkEditor`, with corresponding actions now handled via `KeyBindingManager` and `CommandSystem`, or Lua bindings.
|
|
|
|
|
|
* **Subtask B.5: Enhanced Error Reporting:**
|
|
|
* **Goal:** Provide more informative feedback to the user when command execution fails due to a keybinding.
|
