[Feature]: Configurable terminal scroll sensitivity (expose xterm.js scrollSensitivity)

Open Beginner friendly
#3,431 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
cli

Research direction

Start in frontend/app/view/term/term.tsx, where the terminal options are built and scrollback is currently passed through. Follow the existing term:* configuration pattern, add the two sensitivity settings with their stated defaults, and pass them to the xterm.js options. Done means users can configure normal and fast terminal scroll sensitivity.

Written by the indexing model from the issue text.

Description

enhancement triage
Feature description

Problem. On macOS with a trackpad, terminal scrolling in Wave feels significantly less sensitive than in native terminals (iTerm2/Terminal.app). Long Claude Code / TUI sessions require a lot of finger-dragging to move through scrollback.

Cause. xterm.js supports scrollSensitivity and fastScrollSensitivity options (defaults: 1 and 5), but Wave doesn't expose them — frontend/app/view/term/term.tsx only passes scrollback into terminal options, so users are stuck with the default sensitivity. (Alt+wheel fast-scroll also doesn't seem to kick in on macOS trackpads.)

Environment. Wave 0.14.5, macOS (Darwin 25), trackpad.

Implementation Suggestion

Add two settings keys, passed through to xterm.js options:

  • term:scrollsensitivity (float, default 1)
  • term:fastscrollsensitivity (float, default 5)

Both fit the existing term:* config pattern and are a small change in term.tsx where terminal options are built.

Anything else?

No response

Dominant language
Go
Stars
22.3k
Forks
1.1k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wavetermdev/waveterm

All issues in wavetermdev/waveterm

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.