starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

allow ctrl-v to be overriden #20782

New Issue
Closed
opened 2026-01-31 07:23:55 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 07:23:55 +00:00
Owner
Copy Link

Originally created by @pm100 on GitHub (Nov 7, 2023).

Originally assigned to: @zadjii-msft on GitHub.

Description of the new feature/enhancement

Today regardless of any mode settings ctrl-v is always processed by terminal rather than passing it to the app. This is not convenient because:

  • maybe ctrl-v means something else to the app
  • asymmetry, ctrl-c is passed to the app if ENABLE_PROCESSED_INPUT is off but ctrl-v is not. If I have my own 'clipboard' then the ctrl-v will paste the wrong text
  • with multi line pastes I get a popup dialog warning me (imagine if vs code did this on every paste)
  • The paste comes in as separate keys strokes, not as one operation, so if I support undo then on a 50 char paste I have to press undo 50 times
  • the ctrl-v paste is slow since the app sees it as multiple keystrokes rather than one large insert
  • A large paste might even overflow my undo history stack so its not undoable at all

Others have reported this issue and all the suggestions and proposed solutions are not really useful

  • change the keyboard settings. Problem is that I want ctrl-v to work elsewhere, on the command line say
  • terminal detects the name of the executable (vim.exe), this is plainly not workable
  • only needed for WSL - not enough

Proposed technical implementation details (optional)

either

  • ENABLE_PROCESSED_INPUT=0 should disable ctrl-v as well as ctrl-c. This is a theoretically breaking change
  • a new DONT_PASTE flag in console mode settings
Originally created by @pm100 on GitHub (Nov 7, 2023). Originally assigned to: @zadjii-msft on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Today regardless of any mode settings ctrl-v is always processed by terminal rather than passing it to the app. This is not convenient because: - maybe ctrl-v means something else to the app - asymmetry, ctrl-c is passed to the app if ENABLE_PROCESSED_INPUT is off but ctrl-v is not. If I have my own 'clipboard' then the ctrl-v will paste the wrong text - with multi line pastes I get a popup dialog warning me (imagine if vs code did this on every paste) - The paste comes in as separate keys strokes, not as one operation, so if I support undo then on a 50 char paste I have to press undo 50 times - the ctrl-v paste is slow since the app sees it as multiple keystrokes rather than one large insert - A large paste might even overflow my undo history stack so its not undoable at all Others have reported this issue and all the suggestions and proposed solutions are not really useful - change the keyboard settings. Problem is that I want ctrl-v to work elsewhere, on the command line say - terminal detects the name of the executable (vim.exe), this is plainly not workable - only needed for WSL - not enough # Proposed technical implementation details (optional) either - ENABLE_PROCESSED_INPUT=0 should disable ctrl-v as well as ctrl-c. This is a theoretically breaking change - a new DONT_PASTE flag in console mode settings
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 07:23:55 +00:00
claunia commented 2026-01-31 07:23:56 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 7, 2023):

Today regardless of any mode settings ctrl-v is always processed by terminal
Others have reported this issue and all the suggestions and proposed solutions are not really useful

  • change the keyboard settings. Problem is that I want ctrl-v to work elsewhere, on the command line say

Would you be able to elaborate on this? Deleting the Ctrl+V key binding from Windows Terminal's settings is quick and easy, and doesn't require you to change any keyboard configuration.

Thanks!

@DHowett commented on GitHub (Nov 7, 2023): > Today regardless of any mode settings ctrl-v is always processed by terminal > Others have reported this issue and all the suggestions and proposed solutions are not really useful > * change the keyboard settings. Problem is that I want ctrl-v to work elsewhere, on the command line say Would you be able to elaborate on this? Deleting the <kbd>Ctrl+V</kbd> key binding from Windows Terminal's settings is quick and easy, and doesn't require you to change any keyboard configuration. Thanks!
claunia commented 2026-01-31 07:23:57 +00:00
Author
Owner
Copy Link

@pm100 commented on GitHub (Nov 7, 2023):

I only want it for the app I am writing (just like vim, nano,... that have also complained about the same thing) not globally. ie the app needs to turn it on and off, just like I can turn ctrl-c on and off programmatically. It should not have to be :

  • a global change
  • done by the end user
@pm100 commented on GitHub (Nov 7, 2023): I only want it for the app I am writing (just like vim, nano,... that have also complained about the same thing) not globally. ie the app needs to turn it on and off, just like I can turn ctrl-c on and off programmatically. It should not have to be : - a global change - done by the end user
claunia commented 2026-01-31 07:23:57 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (May 3, 2024):

See also #11267

@j4james commented on GitHub (May 3, 2024): See also #11267
claunia commented 2026-01-31 07:23:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 6, 2024):

You know what? You're absolutely right. This is a /dupe of #11267. We'll consolidate tracking there, thanks!

@zadjii-msft commented on GitHub (Jun 6, 2024): You know what? You're absolutely right. This is a /dupe of #11267. We'll consolidate tracking there, thanks!
claunia commented 2026-01-31 07:23:57 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jun 6, 2024):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Jun 6, 2024): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
claunia commented 2026-01-31 07:23:58 +00:00
Author
Owner
Copy Link

@MogHughson commented on GitHub (Aug 24, 2024):

This issue precisely articulates the problem I am seeing. Did this get fixed? How can an application turn off Ctrl-C and Ctrl-V being grabbed by the terminal while it is running without asking the user to change the settings in the Terminal?

@MogHughson commented on GitHub (Aug 24, 2024): This issue precisely articulates the problem I am seeing. Did this get fixed? How can an application turn off Ctrl-C and Ctrl-V being grabbed by the terminal while it is running without asking the user to change the settings in the Terminal?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20782
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?