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

Copy and Paste Bug while using Ctrl + C and Ctrl + V shortcuts #3399

New Issue
Closed
opened 2026-01-30 23:20:25 +00:00 by claunia · 10 comments
claunia commented 2026-01-30 23:20:25 +00:00
Owner
Copy Link

Originally created by @nabanita-sarkar on GitHub (Aug 13, 2019).

Environment

Windows build number: 1903 for cmd
Windows Terminal version (if applicable): latest from the Microsoft store

Any other software? N/A

Steps to reproduce

Copy any text using keyboard shortcut ctrl + C and try to paste it using ctrl + V shortcut.

Expected behavior

This should paste the copied text in the command line.

Actual behavior

After typing Ctrl + V only ^v is showing.

Originally created by @nabanita-sarkar on GitHub (Aug 13, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 1903 for cmd Windows Terminal version (if applicable): latest from the Microsoft store Any other software? N/A ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Copy any text using keyboard shortcut `ctrl + C` and try to paste it using `ctrl + V` shortcut. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> This should paste the copied text in the command line. # Actual behavior <!-- What's actually happening? --> After typing `Ctrl + V` only `^v` is showing.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-30 23:20:26 +00:00
claunia commented 2026-01-30 23:20:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 13, 2019):

Do you have keybindings for copy and paste set in your profiles.json?

@zadjii-msft commented on GitHub (Aug 13, 2019): Do you have keybindings for `copy` and `paste` set in your `profiles.json`?
claunia commented 2026-01-30 23:20:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 13, 2019):

Also, please refer to the user documentation

@zadjii-msft commented on GitHub (Aug 13, 2019): Also, please refer to [the user documentation](https://github.com/microsoft/terminal/blob/master/doc/user-docs/UsingJsonSettings.md#adding-copy-and-paste-keybindings)
claunia commented 2026-01-30 23:20:27 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 17, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 17, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-30 23:20:27 +00:00
Author
Owner
Copy Link

@dasMulli commented on GitHub (Aug 17, 2019):

Has there been a discussion of changing the defaults to ctrl+c/ctrl+v by default similar to how the default conhost+cmd experience in windows is at the moment? (I assume there is a reason like making a lot of *nix programs hard to use?..)

@dasMulli commented on GitHub (Aug 17, 2019): Has there been a discussion of changing the defaults to ctrl+c/ctrl+v by default similar to how the default conhost+cmd experience in windows is at the moment? (I assume there is a reason like making a lot of *nix programs hard to use?..)
claunia commented 2026-01-30 23:20:28 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 17, 2019):

We explicitly changed the defaults away from Ctrl+C/Ctrl+V because of that reason -- it's hard to use your shell and your CLI applications when your terminal emulator gets in the way by eating common key combos. #2446 goes a long way to fixing this, because it lets you bind Ctrl+C over copy but still send ^C to the connected application when there's no selection; there is, however, no reasonable heuristic we can use for Ctrl+V.

We're trying to make something approachable for Windows and Linux folks, but in some cases the best we can do is choose one option and make it trivially easy to change for the people who disagree.

@DHowett-MSFT commented on GitHub (Aug 17, 2019): We explicitly changed the defaults away from <kbd>Ctrl+C</kbd>/<kbd>Ctrl+V</kbd> _because_ of that reason -- it's hard to use your shell and your CLI applications when your terminal emulator gets in the way by eating common key combos. #2446 goes a long way to fixing this, because it lets you bind <kbd>Ctrl+C</kbd> over copy but still send `^C` to the connected application when there's no selection; there is, however, no reasonable heuristic we can use for <kbd>Ctrl+V</kbd>. We're trying to make something approachable for Windows _and_ Linux folks, but in some cases the best we can do is choose one option and make it trivially easy to change for the people who disagree.
claunia commented 2026-01-30 23:20:28 +00:00
Author
Owner
Copy Link

@nabanita-sarkar commented on GitHub (Aug 19, 2019):

Okay

@nabanita-sarkar commented on GitHub (Aug 19, 2019): Okay
claunia commented 2026-01-30 23:20:28 +00:00
Author
Owner
Copy Link

@onionhammer commented on GitHub (Sep 11, 2019):

@DHowett-MSFT What was wrong w/ how it worked in the other command prompt?

If text is selected CTRL+C copies
if text is not selected CTRL+C sends signal

@onionhammer commented on GitHub (Sep 11, 2019): @DHowett-MSFT What was wrong w/ how it worked in the other command prompt? If text is selected CTRL+C copies if text is not selected CTRL+C sends signal
claunia commented 2026-01-30 23:20:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 11, 2019):

@onionhammer When that comment was authored, the Terminal had a bug where whatever keybinding you had for copy would always try to copy, even if there wasn't a selection. Now that that bug is fixed, we can think about maybe adding Ctrl+C as a default copy keybinding again.

@zadjii-msft commented on GitHub (Sep 11, 2019): @onionhammer When that comment was authored, the Terminal had a bug where whatever keybinding you had for copy would always try to copy, even if there wasn't a selection. Now that that bug is fixed, we can think about maybe adding Ctrl+C as a default copy keybinding again.
claunia commented 2026-01-30 23:20:29 +00:00
Author
Owner
Copy Link

@onionhammer commented on GitHub (Sep 11, 2019):

@zadjii-msft afaict it works perfectly if I just add the key-binding in manually

@onionhammer commented on GitHub (Sep 11, 2019): @zadjii-msft afaict it works perfectly if I just add the key-binding in manually
claunia commented 2026-01-30 23:20:29 +00:00
Author
Owner
Copy Link

@iliveforfun commented on GitHub (Sep 24, 2019):

Also, please refer to the user documentation

already solve my problem but is there a strict format for the definition of such command? cuz when I type a command for copying, error always happens. Although my format looks like other comand

@iliveforfun commented on GitHub (Sep 24, 2019): > Also, please refer to [the user documentation](https://github.com/microsoft/terminal/blob/master/doc/user-docs/UsingJsonSettings.md#adding-copy-and-paste-keybindings) **already solve my problem** but is there a strict format for the definition of such command? cuz when I type a command for copying, error always happens. Although my format looks like other comand
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 Needs-Attention Needs-Tag-Fix Needs-Triage
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#3399
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?