sync: copy-mode big-word motions (upstream #2270)

[OnlineChef (ChefGroep)]

Ports upstream feature copy-mode big-word motions from ogulcancelik/herdr into the GroepOnline fork, as part of the incremental upstream-sync campaign (one feature per PR, stacked).

• Upstream commit: fd0e4ff4 (feat(copy-mode): add big-word motions (#2270))
• Cherry-pick applies cleanly on top of origin/main (no conflicts).
• Files: src/app/input/copy_mode.rs, src/pane/terminal.rs, docs/next/website/src/content/docs/keyboard.mdx.

Verification: CI (notify-first, no local Rust build on laptop) will confirm build + tests. This is a mechanical port of an upstream feature; no fork-specific behavior change.

Stack: this is PR 1 of N in the upstream v0.8.0 feature sync.

[qodo-code-review]

PR Summary by Qodo

Copy mode: add big-word motions (W/B/E) and document behavior

✨ Enhancement 📝 Documentation 🕐 20-40 Minutes

AI Description

• Add tmux-style big-word motions (W/B/E) to copy-mode navigation.
• Extend terminal text scanning to support big-word boundaries across punctuation and rows.
• Document copy-mode movement, search, selection, and copy semantics in keyboard docs.

Diagram

graph TD
  A["App copy-mode input"] --> B["CopyModeState"] --> C["PaneTerminal word scan"] --> D[("Terminal buffer")]
  B --> E["Selection & search"]
  A --> F["Docs: keyboard.mdx"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Implement big-word scanning in copy_mode.rs only

• ➕ Keeps terminal.rs simpler and limits changes to copy-mode feature code
• ➕ Avoids expanding terminal-level APIs/enums
• ➖ Duplicates text-scanning logic already needed for other motions/search
• ➖ Harder to reuse/keep consistent with terminal text semantics across features

2. Use a Unicode segmentation library for word boundaries

• ➕ More correct behavior across scripts and edge cases
• ➕ Potential reuse across search/selection features
• ➖ Adds dependency and integration complexity
• ➖ May not match tmux/zellij expectations for 'big word' semantics (whitespace-delimited)

Recommendation: Keep the current approach: define explicit big-word motion variants in the terminal text-scanning layer and invoke them from copy-mode. This centralizes boundary rules, enables consistent behavior across motions/selection, and matches expected tmux-style semantics while remaining dependency-light.

Files changed (3) +112 / -0 · 2 not counted

Enhancement (2)

copy_mode.rsWire copy-mode key handling to support big-word motions _{not counted}

Wire copy-mode key handling to support big-word motions

• Implements/updates copy-mode key dispatch to include big-word navigation commands (W/B/E) alongside existing tmux-style motions and selection/search behaviors. Includes coverage for big-word motion behavior, including punctuation runs and selection extension.

src/app/input/copy_mode.rs

terminal.rsAdd big-word motion support to terminal text navigation _{not counted}

Add big-word motion support to terminal text navigation

• Extends terminal text scanning with explicit big-word motion variants and separator rules to move to next/previous big-word start/end. Ensures motion logic can traverse punctuation and cross row boundaries to support copy-mode navigation and selection extension.

src/pane/terminal.rs

Documentation (1) +112 / -0

keyboard.mdxDocument copy-mode motions, including big-word W/B/E +112/-0

Document copy-mode motions, including big-word W/B/E

• Adds a dedicated keyboard documentation page and describes copy-mode usage, including standard and big-word motions, search behavior, selection/copy keys, and escape semantics. Notes interaction between copy-mode paging and the configured prefix key.

docs/next/website/src/content/docs/keyboard.mdx

[qodo-code-review]

1. #[cfg(windows)] in terminal.rs 📜 Skill insight ⌂ Architecture

src/pane/terminal.rs contains Windows-specific conditional compilation outside src/platform/.

This violates the platform code placement rule and risks further OS-specific logic spreading into

core modules.

Details

Agent Prompt

```
## Issue description
src/pane/terminal.rs includes Windows-specific code gated by `#[cfg(windows)]`, but compliance requires platform-specific code to live under `src/platform/`.

## Issue Context
This file currently declares a Windows-only module (windows_recent_fallback) directly under src/pane/, which violates the platform-code containment requirement.

## Fix Focus Areas
- src/pane/terminal.rs[19-21]
```

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[qodo-code-review]

2. Stable keyboard.mdx added 📜 Skill insight § Compliance

New keyboard documentation (including copy-mode/big-word behavior) was added under the stable docs

tree website/src/content/docs/. Unreleased feature docs must live only under docs/next/ and not

in the stable website docs.

Details

Agent Prompt

```
## Issue description
Documentation describing new/unreleased behavior was added to the stable docs tree (website/src/content/docs/). Unreleased work must be documented only in `docs/next/`.

## Issue Context
This PR already adds the keyboard doc under docs/next/website/...; the stable website/... copy should not be introduced for unreleased changes.

## Fix Focus Areas
- website/src/content/docs/keyboard.mdx[65-67]
```

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[qodo-code-review]

3. Readme changed without request 📘 Rule violation § Compliance

README.md is modified in this PR, but normal feature/fix branches must not change root README

unless explicitly requested/declared for the work item. This can create unreviewed docs/metadata

drift unrelated to the feature port.

Details

Agent Prompt

```
## Issue description
This PR modifies README.md, but the compliance rule requires such edits to be explicitly part of the task request.

## Issue Context
If the README update is intentional for this work item, it must be explicitly called out; otherwise it should be reverted/split into a dedicated docs PR.

## Fix Focus Areas
- README.md[8-11]
```

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[qodo-code-review]

4. Root changelog modified 📜 Skill insight ⚙ Maintainability

CHANGELOG.md has been modified (cleared) as part of this PR, but unreleased feature work must not

touch the root changelog. Changelog updates for unreleased work should be kept under docs/next/ or

deferred to the release process.

Details

Agent Prompt

```
## Issue description
This PR changes the root CHANGELOG.md, which is disallowed for unreleased feature work.

## Issue Context
Keep unreleased documentation/changelog material under docs/next/ (or omit until release), and avoid altering the stable root changelog in feature PRs.

## Fix Focus Areas
- CHANGELOG.md[1-4]
```

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[qodo-code-review]

5. Paragraph motion clamped to 1000-row scan limit 🐞 Bug ≡ Correctness

copy_mode_paragraph() clamps its scan limit to at most 1000 rows via .clamp(1, 1000), so {/}
paragraph motion silently stops before reaching an actual blank-line boundary in panes with more
than 1000 rows of scrollback/viewport. The user gets no feedback that the search was truncated; the
cursor just stops mid-buffer as if a boundary was found.

Agent Prompt

## Issue description
copy_mode_paragraph()'s scan loop limit is clamped to a maximum of 1000 rows regardless of how large the pane's actual scrollback is, so `{`/`}` paragraph motions can silently stop before reaching a real paragraph boundary in large scrollback buffers, with no indication to the user that the search was truncated.

## Issue Context
The limit is computed from `pane_scroll_metrics(...).max_offset_from_bottom + viewport_rows` and then hard-clamped with `.clamp(1, 1000)`. For scrollback buffers larger than ~1000 rows, this cap prevents `copy_mode_paragraph` from scanning the full buffer.

## Fix Focus Areas
- src/app/input/copy_mode.rs[693-707]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[qodo-code-review]

Qodo Fixer

✅ Committed (4) · ☑ Fixed (4)

Commits pushed directly to this PR — no separate fix PR opened.

Process — 4 fixed

• ☑ Fixed: #[cfg(windows)] in terminal.rs
• ☑ Fixed: Stable keyboard.mdx added
• ☑ Fixed: README changed without request
• ☑ Fixed: Root CHANGELOG modified