starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Implement CTRL V "Safe Paste" from Windows PowerShell console #9440

New Issue
Closed
opened 2026-01-31 01:54:32 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 01:54:32 +00:00
Owner
Copy Link

Originally created by @yllekz on GitHub (Jul 4, 2020).

Description of the new feature/enhancement

Windows PowerShell in Windows 10 allows you to paste code using CTRL V without the lines immediately executing.
Windows Terminal doesn't appear to have this feature yet, as the only method of pasting content (unless it's PowerShell) is right clicking, and if you have multiple lines, the lines execute immediately.
I would love if the CTRL V "safe paste" feature from the Windows PowerShell console could be implemented.

Proposed technical implementation details (optional)

Press CTRL V; the contents are put into the line, but are not immediately executed.

The contents are put into the line, but are not immediately executed, especially if the paste queue is multi-line.

Originally created by @yllekz on GitHub (Jul 4, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Windows PowerShell in Windows 10 allows you to paste code using CTRL V without the lines immediately executing. Windows Terminal doesn't appear to have this feature yet, as the only method of pasting content (unless it's PowerShell) is right clicking, and if you have multiple lines, the lines execute immediately. I would love if the CTRL V "safe paste" feature from the Windows PowerShell console could be implemented. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) Press CTRL V; the contents are put into the line, but are not immediately executed. <!-- A clear and concise description of what you want to happen. --> The contents are put into the line, but are not immediately executed, especially if the paste queue is multi-line.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:54:32 +00:00
claunia commented 2026-01-31 01:54:33 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Jul 5, 2020):

Just remove the Ctrl+V binding from settings.json of Windows Terminal. Then, Windows Terminal will pass the Ctrl+V key combination to PSReadLine, and you will have your "safe paste" feature.

It might be better if Windows Terminal did not add the Ctrl+C and Ctrl+V bindings to settings.json in the first place.

@KalleOlaviNiemitalo commented on GitHub (Jul 5, 2020): Just remove the Ctrl+V binding from `settings.json` of Windows Terminal. Then, Windows Terminal will pass the Ctrl+V key combination to PSReadLine, and you will have your "safe paste" feature. It might be better if Windows Terminal did not add the Ctrl+C and Ctrl+V bindings to `settings.json` in the first place.
claunia commented 2026-01-31 01:54:34 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 5, 2020):

might be better if

You and I agree on that point, but exactly 50% of our community will riot regardless of which paste option we make default (or which option we detect and pop up a dialog box about).

@DHowett commented on GitHub (Jul 5, 2020): > might be better if You and I agree on that point, but exactly 50% of our community will riot regardless of which paste option we make default (or which option we detect and pop up a dialog box about).
claunia commented 2026-01-31 01:54:34 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 5, 2020):

@KalleOlaviNiemitalo is correct. Letting PSReadline handle this binding will work great if you only use powershell.
If you don’t, follow /dup #395.

@DHowett commented on GitHub (Jul 5, 2020): @KalleOlaviNiemitalo is correct. Letting PSReadline handle this binding will work great if you only use powershell. If you don’t, follow /dup #395.
claunia commented 2026-01-31 01:54:34 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 5, 2020):

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!

@ghost commented on GitHub (Jul 5, 2020): 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!
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#9440
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?