Configurable keymaps, colors

[jadonwb]

Hello, I have noticed that keymaps and colors are not configurable right now, the main navigation works for me since I use vim, but often times people who don't use qwerty need to remap hjkl to something else. I also personally like ^ to be start of line instead of 0.

Also I like that it uses my terminal colors, but I would like to be able to pick some of those choices, like markdown headers, or tweak the highlight color. I use a light theme and the current choice of color for selection/visual/highlight is kinda hard to read.

I am willing to tackle this myself if that is okay, but I thought I would mention it here in case you have a preferred way of doing this.

I haven't explored the source too deeply yet so it won't be immediate if I do take a look (and I'm busy this next week or so).

[backnotprop]

Accepted, and yes, please take it. No rush; a week or two is fine.

A few notes so you can build against the shape we'd merge:

Config. There's already a strict TOML config at ~/.config/plannotator-tui/config.toml (see crates/plannotator-tui/src/config.rs). Add [keys] and [colors] tables there rather than new files. Keep the existing rules: deny_unknown_fields, defaults identical to today's behavior, and an unknown key, action name, or color string is an error that names it. plannotator-tui config should print the effective values.

Keys. All bindings live in crates/plannotator-tui/src/app/input.rs, one dispatch per mode. Map action names to a list of keys, e.g.

[keys]
left = ["h", "Left"]
line-start = ["^", "Home"]

so a user can rebind hjkl without losing the arrow keys. The README key table is the list of actions; please keep it in sync.

Colors. Name the semantic roles we actually have rather than a theme engine: heading, selection, cursor, comment, looks-good, delete, and the toolbar/header backgrounds. Constants are at the top of app/draw.rs, app/header.rs, and layout.rs. Accept the usual ratatui color strings (yellow, #ffcc00, 238). The selection is currently REVERSED, which is the light-theme problem you're hitting, so making that a real style is the right fix.

Two PRs, keys first, is easiest to review. Tests are plain unit tests next to the code, and cargo test plus cargo clippy gate CI. Ask here if anything in the source is unclear.