Skip to content

fix(tui): route Home/End to readline composer instead of transcript viewport#124

Merged
shayne-snap merged 1 commit into
mainfrom
feat/readline-home-end
May 25, 2026
Merged

fix(tui): route Home/End to readline composer instead of transcript viewport#124
shayne-snap merged 1 commit into
mainfrom
feat/readline-home-end

Conversation

@shayne-snap
Copy link
Copy Markdown
Contributor

Home and End were previously grouped with PgUp/PgDn as transcript-scroll keys (jumping to buffer top/bottom). After the readline alignment they should move the cursor to start/end of the current line within the composer — the same as Ctrl+A/Ctrl+E.

Changes:

  • model_keys.go: remove home and end from the pgup/pgdown scroll case in chat mode
  • composer_test.go: add TestComposerHomeAndEndMoveWithinCurrentLine
  • model_test.go: rename/update scroll key test to assert Home/End no longer affect the transcript; update downstream tests to call handleViewportScrollKey directly

Testing:

  • make test passes (existing + new tests)

…iewport

Home and End were previously grouped with PgUp/PgDn as transcript-scroll
keys (jumping to buffer top/bottom). After the readline alignment they
should move the cursor to start/end of the current line within the
composer — the same as Ctrl+A/Ctrl+E.

- model_keys.go: remove 'home' and 'end' from the pgup/pgdown scroll case
- composer_test.go: add TestComposerHomeAndEndMoveWithinCurrentLine
- model_test.go: rename and update the scroll key test to assert that
  Home/End no longer affect the transcript viewport; update downstream
  tests to call handleViewportScrollKey directly
@shayne-snap shayne-snap merged commit cb42892 into main May 25, 2026
2 checks passed
@shayne-snap shayne-snap deleted the feat/readline-home-end branch May 25, 2026 04:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant