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

Pasting into PowerShell running in Windows Terminal drops Unicode characters #12205

New Issue
Closed
opened 2026-01-31 03:08:59 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 03:08:59 +00:00
Owner
Copy Link

Originally created by @sba923 on GitHub (Jan 26, 2021).

Environment

Windows build number: 10.0.18363.1256
Windows Terminal version (if applicable): 1.4.3243.0
PowerShell 7.1.1
Windows PowerShell 5.1
PSReadLine 2.2.0 beta1

Steps to reproduce

  1. Put the following string on the clipboard: C:\tmp\Captures d’écran where the ’ is U+2019

(Verify as follows:

PS> $p=(Get-ClipboardText); for($i=0;$i -lt $p.Length; $i++) { '{0} {1:x4}' -f $p[$i], [int]($p[$i]) }
C 0043
: 003a
\ 005c
t 0074
m 006d
p 0070
\ 005c
C 0043
a 0061
p 0070
t 0074
u 0075
r 0072
e 0065
s 0073
  0020
d 0064
’ 2019
é 00e9
c 0063
r 0072
a 0061
n 006e

)

  1. Create a folder with this name e.g. using mkdir -Force (Get-ClipboardText) in PowerShell.
  2. In a PowerShell 7.1.1 or Windows PowerShell 5.1 session, type gci " followed by Ctrl+V followed by " followed by Enter.

Expected behavior

Whether PowerShell runs standalone or within Windows Terminal, this should work and show the contents of the C:\tmp\Captures d’écran folder.

Actual behavior

If PowerShell runs within Windows Terminal, the paste action drops the U+2019 character, resulting in an error:

PS> gci "C:\tmp\Captures décran"
Get-ChildItem: Cannot find path 'C:\tmp\Captures décran' because it does not exist.

The paste action works fine in a CMD prompt running within Windows Terminal.

Could that be the result of an interaction / incompatibility between PSReadLine and Windows Terminal?

Originally created by @sba923 on GitHub (Jan 26, 2021). # Environment ```none Windows build number: 10.0.18363.1256 Windows Terminal version (if applicable): 1.4.3243.0 PowerShell 7.1.1 Windows PowerShell 5.1 PSReadLine 2.2.0 beta1 ``` # Steps to reproduce 1. Put the following string on the clipboard: `C:\tmp\Captures d’écran` where the `’` is U+2019 (Verify as follows: ```` PS> $p=(Get-ClipboardText); for($i=0;$i -lt $p.Length; $i++) { '{0} {1:x4}' -f $p[$i], [int]($p[$i]) } C 0043 : 003a \ 005c t 0074 m 006d p 0070 \ 005c C 0043 a 0061 p 0070 t 0074 u 0075 r 0072 e 0065 s 0073 0020 d 0064 ’ 2019 é 00e9 c 0063 r 0072 a 0061 n 006e ```` ) 2. Create a folder with this name e.g. using `mkdir -Force (Get-ClipboardText)` in PowerShell. 3. In a PowerShell 7.1.1 or Windows PowerShell 5.1 session, type `gci "` followed by `Ctrl+V` followed by `"` followed by `Enter`. # Expected behavior Whether PowerShell runs standalone or within Windows Terminal, this should work and show the contents of the `C:\tmp\Captures d’écran` folder. # Actual behavior If PowerShell runs within Windows Terminal, the paste action drops the U+2019 character, resulting in an error: ```` PS> gci "C:\tmp\Captures décran" Get-ChildItem: Cannot find path 'C:\tmp\Captures décran' because it does not exist. ```` The paste action works fine in a `CMD` prompt running within Windows Terminal. Could that be the result of an interaction / incompatibility between PSReadLine and Windows Terminal?
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-FixProduct-Powershell labels 2026-01-31 03:08:59 +00:00
claunia commented 2026-01-31 03:09:02 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Jan 26, 2021):

May be a duplicate of https://github.com/PowerShell/PSReadLine/issues/1603. The workaround would be to remove the Ctrl+V key binding from settings.json of Windows Terminal so that WT passes the key combination to PowerShell, where PSReadLine then implements the paste feature correctly.

@KalleOlaviNiemitalo commented on GitHub (Jan 26, 2021): May be a duplicate of <https://github.com/PowerShell/PSReadLine/issues/1603>. The workaround would be to remove the Ctrl+V key binding from settings.json of Windows Terminal so that WT passes the key combination to PowerShell, where PSReadLine then implements the paste feature correctly.
claunia commented 2026-01-31 03:09:02 +00:00
Author
Owner
Copy Link

@sba923 commented on GitHub (Jan 26, 2021):

I confirm removing the Ctrl+V binding from settings.json and then using Ctrl+V to paste causes the pasting to be correct.

But won't this affect other (non-PowerShell/PSReadLine) scenarios?

And this doesn't "fix" pasting with Shift+Ins or right mouse-click.

@sba923 commented on GitHub (Jan 26, 2021): I confirm removing the `Ctrl+V` binding from `settings.json` and then using `Ctrl+V` to paste causes the pasting to be correct. But won't this affect other (non-PowerShell/PSReadLine) scenarios? And this doesn't "fix" pasting with `Shift+Ins` or right mouse-click.
claunia commented 2026-01-31 03:09:02 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Jan 26, 2021):

But won't this affect other (non-PowerShell/PSReadLine) scenarios?

Yes, it will. You can then use Ctrl+V to paste to PSReadLine, and Shift+Insert or Ctrl+Shift+V to paste to other software.

I guess another workaround would be to uninstall PSReadLine until https://github.com/PowerShell/PSReadLine/issues/1603 is fixed.

@KalleOlaviNiemitalo commented on GitHub (Jan 26, 2021): > But won't this affect other (non-PowerShell/PSReadLine) scenarios? Yes, it will. You can then use Ctrl+V to paste to PSReadLine, and Shift+Insert or Ctrl+Shift+V to paste to other software. I guess another workaround would be to uninstall PSReadLine until <https://github.com/PowerShell/PSReadLine/issues/1603> is fixed.
claunia commented 2026-01-31 03:09:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 26, 2021):

(I'm gonna resolve this as a dup of the upstream issue, but feel free to continue the conversation. Thanks!)

@zadjii-msft commented on GitHub (Jan 26, 2021): (I'm gonna resolve this as a dup of the upstream issue, but feel free to continue the conversation. Thanks!)
claunia commented 2026-01-31 03:09:03 +00:00
Author
Owner
Copy Link

@sba923 commented on GitHub (Jan 26, 2021):

But won't this affect other (non-PowerShell/PSReadLine) scenarios?

Yes, it will. You can then use Ctrl+V to paste to PSReadLine, and Shift+Insert or Ctrl+Shift+V to paste to other software.

I guess another workaround would be to uninstall PSReadLine until PowerShell/PSReadLine#1603 is fixed.

Unininstalling PSReadLine? That would be cutting my right arm! 😆

@sba923 commented on GitHub (Jan 26, 2021): > > But won't this affect other (non-PowerShell/PSReadLine) scenarios? > > Yes, it will. You can then use Ctrl+V to paste to PSReadLine, and Shift+Insert or Ctrl+Shift+V to paste to other software. > > I guess another workaround would be to uninstall PSReadLine until [PowerShell/PSReadLine#1603](https://github.com/PowerShell/PSReadLine/issues/1603) is fixed. Unininstalling PSReadLine? That would be cutting my right arm! 😆
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-Tag-Fix Needs-Triage Product-Powershell Resolution-External
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#12205
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?