Find, select & copy text within blocks with keyboard only (similar to vi or tmux copy-mode)

Open
#3,436 12 comments 53 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
cli

Research direction

No files, tests, or entry points are named in the issue. Start by locating Warp’s terminal block text-selection and keyboard-input handling, then define the scope for vi/tmux-like navigation, search, marking, and clipboard yanking; done means the complete workflow works without mouse or trackpad.

Written by the indexing model from the issue text.

Description

area:settings-keybindings enhancement triaged
Discord username (optional)

No response

Describe the solution you'd like?
Hey, I couldn't find a similar issue, maybe I've missed it.

My current workflow in iTerm2 + tmux that I cannot reproduce with Warp are:
- Entering copy-mode manually (`prefix` + `[`), navigating using keyboard, marking wanted text and yanking it to clipboard
- Finding (`prefix` + `/`) some text, marking the substring, click 'n' or 'N' until I find the correct place in buffer, marking around it as needed and yanking it into clipboard.

For me personally this flow is so important that it is the only thing that prevents me from fully switching over to Warp.
Is your feature request related to a problem? Please describe.
It may be only a personal pet peeve but using the mouse/trackpad is very awkward and uncomfortable, I'm used to using the above keyboard shortcuts. I believe this can be a great UX improvement.
Additional context

No response

How important is this feature to you?

4

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

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 warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.