Repository navigation
feat(terminal): use Ctrl+V for paste - #9201
davidvornholt wants to merge 1 commit into
Conversation
ApprovabilityVerdict: Not approved Macroscope's review found this PR not approvable — This changes the built-in non-macOS terminal behavior for Ctrl+V, causing the shortcut to invoke asynchronous clipboard paste instead of reaching the shell. An unresolved review comment identifies a concrete risk that ordinary left-Control Ctrl+V input is intercepted, so the behavior change needs human review. You can add or adjust custom eligibility rules. Learn more. |
5211ced to
ba6c026
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ba6c026. Configure here.
| } | ||
| if (key !== "v") return false; | ||
| return isMacPlatform(platform) ? event.metaKey : event.ctrlKey && event.shiftKey; | ||
| return isMacPlatform(platform) ? event.metaKey : event.ctrlKey; |
There was a problem hiding this comment.
Left Ctrl+V intercepted as paste
High Severity
isTerminalPasteShortcut now treats any non-macOS ctrlKey+V as paste, so Left Ctrl+V is swallowed instead of reaching the shell. The change is meant to paste only when Right Control or Shift is held, and no Right Control tracking exists to make that distinction.
Reviewed by Cursor Bugbot for commit ba6c026. Configure here.
There was a problem hiding this comment.
Thanks for flagging this. The behavior described here is intentional rather than a missing side check.\n\nAn earlier revision distinguished Right Ctrl so Left Ctrl+V could continue reaching the shell. After testing the actual workflow, I simplified the proposal: on Linux and Windows, ordinary Ctrl+V should paste, matching browsers and editors and making physical Ctrl+V and Caps-as-Ctrl+V behave consistently.\n\nThe tradeoff is that Ctrl+V no longer invokes terminal quoted insert. That is documented in the PR description. Ctrl+Shift+V and Shift+Insert remain supported.\n\nIf preserving shell Ctrl+V is a project requirement, this PR should not merge in its current form—or the behavior would need to become configurable. Restoring Right-Control tracking would implement a different, more specialized behavior than this PR now proposes.
|
Note This comment is posted by Julius' dot This PR intentionally replaces terminal quoted insert with clipboard paste for Ctrl+V on Linux and Windows, and the description says users must rebind quoted insert. That changes a product default, but the PR and discussion contain no explicit maintainer approval of that direction. The prior approval requirement applies. Closing this for now; agree on the shortcut behavior and scope with maintainers in an Ideas discussion, link their approval, then request reconsideration. |


What changed
On Linux and Windows, Ctrl+V now pastes clipboard text into T3 Code's embedded terminal. Ctrl+Shift+V and Shift+Insert still work, and Cmd+V is unchanged on macOS.
Why
Ctrl+V means paste throughout T3 Code and in most desktop apps. In the embedded terminal, however, it currently sends
^Vto the shell and starts quoted input. That mismatch is easy to trip over, especially when Caps Lock is mapped to Control for familiar Caps+C and Caps+V shortcuts.This change makes the physical Control key and a remapped Caps Lock behave consistently. It intentionally changes the terminal's quoted-insert shortcut. Users who need quoted insert will have to bind it to another key.
Testing