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

Terminal doesn't copy on Enter (like conhost does) #6780

New Issue
Open
opened 2026-01-31 00:47:07 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 00:47:07 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Mar 8, 2020).

Description of the Bug:
When we work on Command Prompt or PowerShell without using Windows Terminal, we have the option of copying text by selecting it and pressing Enter key. Later, we can paste the text whenever required by right-clicking anywhere inside the window. But Windows Terminal does not allow us to work in a similar manner. When we select any text inside Windows Terminal and press Enter key to copy it, it simply jumps to a new command (carriage return) without actually saving the text to the clipboard.

This issue may seem similar to #4835, #4149, #2340 and #4621. All those issues focus that the shortcuts Ctrl+C or Ctrl+V are not working. These issues can be fixed by adjusting the keybindings, but the current issue has not been fixed as per my knowledge.

Steps to Reproduce:

  1. Press [Win]+R, type ‘powershell.exe’ and hit Enter.
  2. Type in the following commands:
Import-Module PackageManagement
Get-Command -Module PackageManagement
  1. Select any command, for example ‘Install-Package’ using the mouse.
  2. Press enter to copy it.
  3. Then right-click anywhere inside the window. You will see the command pasted.
  4. Press [Win]+V to check the clipboard history. You will see the latest entry as ‘Install-Package’. Delete that entry.
  5. Now repeat the same steps by running PowerShell inside Windows Terminal. Notice the difference. Don’t forget to check the clipboard history again.

Expected Behaviour:
The Terminal should have copied the text on pressing Enter. The copied text should have been visible inside Clipboard History. It should not jump to a new command (carriage return).

Screenshots:

  1. For ‘powershell.exe’

image
image

  1. For Powershell inside Windows Terminal

image
image

Device and Application Information:
• OS Build: 10.0.18362.657
• Architecture: x64
• Application Version: 0.9.433.0
• Region: New Delhi, India
• Dev Version Installed: False

I’m just reporting the problem. I don’t want to fix it.

Originally created by @ghost on GitHub (Mar 8, 2020). **Description of the Bug**: When we work on Command Prompt or PowerShell without using Windows Terminal, we have the option of copying text by selecting it and pressing Enter key. Later, we can paste the text whenever required by right-clicking anywhere inside the window. But Windows Terminal does not allow us to work in a similar manner. When we select any text inside Windows Terminal and press Enter key to copy it, it simply jumps to a new command (carriage return) without actually saving the text to the clipboard. This issue may seem similar to #4835, #4149, #2340 and #4621. All those issues focus that the shortcuts Ctrl+C or Ctrl+V are not working. These issues can be fixed by adjusting the keybindings, but the current issue has not been fixed as per my knowledge. **Steps to Reproduce**: 1. Press [Win]+R, type ‘powershell.exe’ and hit Enter. 2. Type in the following commands: ``` Import-Module PackageManagement Get-Command -Module PackageManagement ``` 3. Select any command, for example ‘Install-Package’ using the mouse. 4. Press enter to copy it. 5. Then right-click anywhere inside the window. You will see the command pasted. 6. Press [Win]+V to check the clipboard history. You will see the latest entry as ‘Install-Package’. Delete that entry. 7. Now repeat the same steps by running PowerShell inside Windows Terminal. Notice the difference. Don’t forget to check the clipboard history again. **Expected Behaviour**: The Terminal should have copied the text on pressing Enter. The copied text should have been visible inside Clipboard History. It should not jump to a new command (carriage return). **Screenshots**: 1. For ‘powershell.exe’ ![image](https://user-images.githubusercontent.com/55381546/76166963-f27dd200-6188-11ea-888f-954869caf17b.png) ![image](https://user-images.githubusercontent.com/55381546/76166973-04f80b80-6189-11ea-9fa9-645fb7e2db37.png) 2. For Powershell inside Windows Terminal ![image](https://user-images.githubusercontent.com/55381546/76166982-14775480-6189-11ea-9a1f-671bf160a275.png) ![image](https://user-images.githubusercontent.com/55381546/76166984-20fbad00-6189-11ea-8221-2716c0df2029.png) **Device and Application Information**: • OS Build: 10.0.18362.657 • Architecture: x64 • Application Version: 0.9.433.0 • Region: New Delhi, India • Dev Version Installed: False I’m just reporting the problem. I don’t want to fix it.
claunia added the Resolution-By-DesignArea-SettingsNeeds-Tag-FixProduct-Terminal labels 2026-01-31 00:47:07 +00:00
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 Area-Settings Needs-Tag-Fix Product-Terminal Resolution-By-Design
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#6780
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?