barrettruth/delta

Fork 0

product: restore keybinding discoverability after customization removal #328

New issue

Closed

opened 2026-05-11 19:25:33 +00:00 by barrettruth · 1 comment

barrettruth commented

2026-05-11 19:25:33 +00:00

Owner

Parent: #305
Related: #239, #324

Problem

After removing keymap customization, it is no longer clear where users can view the built-in keyboard bindings. This is especially noticeable for navigation bindings such as moving through week/month views.

g? was expected to show keybindings or keyboard help, but it currently routes to generic settings. That makes the app feel like it lost discoverability even if the actual bindings still exist.

Open Debate

This is an open debate with no clear-cut solution. We need to decide what the smallest durable product surface should be now that customization is gone.

Possible directions:

Restore a read-only keyboard shortcuts/help modal.
Add a dedicated keybindings/help section inside settings.
Route g? to contextual keyboard help instead of generic settings.
Expose shortcuts through a command-palette/help surface.
Keep settings as the destination, but make keyboard bindings a first-class visible section there.

Non-Goals

Do not reintroduce user-customizable keymaps as part of this issue.
Do not expand the app scope beyond discoverability of the bindings that still exist.

Acceptance

There is a visible way to inspect the active built-in keybindings.
Week/month traversal shortcuts are documented in that surface.
g? has an intentional destination, even if the final decision is not a standalone modal.
The final choice is captured in the issue before implementation proceeds.

Parent: #305 Related: #239, #324 ## Problem After removing keymap customization, it is no longer clear where users can view the built-in keyboard bindings. This is especially noticeable for navigation bindings such as moving through week/month views. `g?` was expected to show keybindings or keyboard help, but it currently routes to generic settings. That makes the app feel like it lost discoverability even if the actual bindings still exist. ## Open Debate This is an open debate with no clear-cut solution. We need to decide what the smallest durable product surface should be now that customization is gone. Possible directions: - Restore a read-only keyboard shortcuts/help modal. - Add a dedicated keybindings/help section inside settings. - Route `g?` to contextual keyboard help instead of generic settings. - Expose shortcuts through a command-palette/help surface. - Keep settings as the destination, but make keyboard bindings a first-class visible section there. ## Non-Goals - Do not reintroduce user-customizable keymaps as part of this issue. - Do not expand the app scope beyond discoverability of the bindings that still exist. ## Acceptance - There is a visible way to inspect the active built-in keybindings. - Week/month traversal shortcuts are documented in that surface. - `g?` has an intentional destination, even if the final decision is not a standalone modal. - The final choice is captured in the issue before implementation proceeds.

barrettruth added this to the v0.1.0 milestone

2026-05-11 19:25:33 +00:00

barrettruth added the

track:ui

type:research

labels

2026-05-11 19:25:33 +00:00

barrettruth referenced this issue

2026-05-11 19:26:06 +00:00

ui cleanup after scope reduction #239

barrettruth referenced this issue

2026-05-11 19:26:06 +00:00

tracker: blank-start cleanup and foundation migration #305

barrettruth referenced this issue from a pull request that will close it,

2026-05-11 19:41:42 +00:00

fix: restore keyboard shortcut discovery #331

barrettruth commented

2026-05-11 19:42:06 +00:00

Author

Owner

Product direction chosen in PR #331: restore read-only shortcut discoverability with a keyboard shortcuts dialog backed by the existing static keymap definitions. g? opens that surface; S remains settings; no keymap customization is reintroduced.

Product direction chosen in PR #331: restore read-only shortcut discoverability with a keyboard shortcuts dialog backed by the existing static keymap definitions. `g?` opens that surface; `S` remains settings; no keymap customization is reintroduced.

barrettruth closed this issue

2026-05-11 19:43:06 +00:00

barrettruth referenced this issue from a commit

2026-05-11 19:43:07 +00:00

fix: restore keyboard shortcut discovery (#331)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

barrettruth/delta#328

No description provided.

Rows
Columns