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

Can't copy correctly when a folder or a file that contains Japanese dot (。) dragged to Windows Terminal or the path is copied from Windows Explorer to Windows Terminal #13102

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

Originally created by @AlifianK on GitHub (Mar 19, 2021).

Windows Terminal can't copy correctly when a folder or a file that contains a Japanese dot or full stop (。) dragged or the path copied from Windows Explorer. I've tried the same folder with Windows PowerShell and Powershell but it seems it only affects Windows Terminal.
I've tried using Get-ChildItem to check, and it displayed the folder correctly

PS D:\> Get-ChildItem

    Directory: D:\

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----          26/02/2021    16:32                Data
d----          05/01/2021    19:13                Games
d----          29/01/2021     6:39                Master
d----          23/02/2021    22:32                Multimedia
d----          07/11/2020    12:10                SUPERVISI MUTU LPMP
d----          03/03/2021    15:03                Tools
d----          05/03/2021    19:16                君の名は。 (Deluxe Edition)
-a---          17/08/2020    22:22         193632 JADWAL PELAJARAN DAN LAPORAN MATERI AJAR BDR SMP 5.docx
-a---          30/12/2019     8:55         403928 TIME TABLE GANIJIL TATAPMUKA.roz

when I tried to change the directory to 君の名は。 (Deluxe Edition) via dragging the folder or copying the folder path from Windows Explorer, Windows Terminal can't do it.

PS D:\> Set-Location "D:\君の名は (Deluxe Edition)"
Set-Location: Cannot find path 'D:\君の名は (Deluxe Edition)' because it does not exist.

notice that Windows Terminal didn't display (。) at all.

Then I typed (。) manually or copied (。) separately from the folder name and it worked

PS D:\> Set-Location "D:\君の名は (Deluxe Edition)"
Set-Location: Cannot find path 'D:\君の名は (Deluxe Edition)' because it does not exist.
PS D:\> Set-Location "D:\君の名は。 (Deluxe Edition)"
PS D:\君の名は。 (Deluxe Edition)>

Environment

Windows build number: 10.0.19042.0
Windows Terminal version (if applicable): 1.6.10571.0

Steps to reproduce

Name a folder with Japanese full stop

a。

then drag the folder or copy the folder path from Windows Explorer or to Windows Terminal then run Set-Location or cd command to go to the folder

Expected behavior

Windows Terminal read the folder path correctly

PS D:\> Set-Location "D:\君の名は。 (Deluxe Edition)"
PS D:\君の名は。 (Deluxe Edition)>

Actual behavior

Windows Terminal doesn't display (。) at all when the folder is dragged or when the directory path is copied or when the folder name is copied

PS D:\> Set-Location "D:\君の名は。 (Deluxe Edition)"

becomes

PS D:\> Set-Location "D:\君の名は (Deluxe Edition)"
Originally created by @AlifianK on GitHub (Mar 19, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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. --> Windows Terminal can't copy correctly when a folder or a file that contains a Japanese dot or full stop (。) dragged or the path copied from Windows Explorer. I've tried the same folder with Windows PowerShell and Powershell but it seems it only affects Windows Terminal. I've tried using ```Get-ChildItem``` to check, and it displayed the folder correctly ``` PS D:\> Get-ChildItem Directory: D:\ Mode LastWriteTime Length Name ---- ------------- ------ ---- d---- 26/02/2021 16:32 Data d---- 05/01/2021 19:13 Games d---- 29/01/2021 6:39 Master d---- 23/02/2021 22:32 Multimedia d---- 07/11/2020 12:10 SUPERVISI MUTU LPMP d---- 03/03/2021 15:03 Tools d---- 05/03/2021 19:16 君の名は。 (Deluxe Edition) -a--- 17/08/2020 22:22 193632 JADWAL PELAJARAN DAN LAPORAN MATERI AJAR BDR SMP 5.docx -a--- 30/12/2019 8:55 403928 TIME TABLE GANIJIL TATAPMUKA.roz ``` when I tried to change the directory to ```君の名は。 (Deluxe Edition)``` via dragging the folder or copying the folder path from Windows Explorer, Windows Terminal can't do it. ``` PS D:\> Set-Location "D:\君の名は (Deluxe Edition)" Set-Location: Cannot find path 'D:\君の名は (Deluxe Edition)' because it does not exist. ``` notice that Windows Terminal didn't display (。) at all. Then I typed (。) manually or copied (。) separately from the folder name and it worked ``` PS D:\> Set-Location "D:\君の名は (Deluxe Edition)" Set-Location: Cannot find path 'D:\君の名は (Deluxe Edition)' because it does not exist. PS D:\> Set-Location "D:\君の名は。 (Deluxe Edition)" PS D:\君の名は。 (Deluxe Edition)> ``` # Environment ```none Windows build number: 10.0.19042.0 Windows Terminal version (if applicable): 1.6.10571.0 ``` # Steps to reproduce Name a folder with Japanese full stop ``` a。 ``` then drag the folder or copy the folder path from Windows Explorer or to Windows Terminal then run ```Set-Location``` or ```cd``` command to go to the folder # Expected behavior Windows Terminal read the folder path correctly ``` PS D:\> Set-Location "D:\君の名は。 (Deluxe Edition)" PS D:\君の名は。 (Deluxe Edition)> ``` # Actual behavior Windows Terminal doesn't display (。) at all when the folder is dragged or when the directory path is copied or when the folder name is copied ``` PS D:\> Set-Location "D:\君の名は。 (Deluxe Edition)" ``` becomes ``` PS D:\> Set-Location "D:\君の名は (Deluxe Edition)" ```
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:33:57 +00:00
claunia commented 2026-01-31 03:33:58 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 19, 2021):

If you remove-module psreadline, does it work?

@DHowett commented on GitHub (Mar 19, 2021): If you `remove-module psreadline`, does it work?
claunia commented 2026-01-31 03:33:58 +00:00
Author
Owner
Copy Link

@AlifianK commented on GitHub (Mar 20, 2021):

It worked.

@AlifianK commented on GitHub (Mar 20, 2021): It worked.
claunia commented 2026-01-31 03:33:58 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 20, 2021):

Okay, this is a well known bug with PSReadline where it deletes certain characters when they are inserted.

@DHowett commented on GitHub (Mar 20, 2021): Okay, this is a well known bug with PSReadline where it deletes certain characters when they are inserted.
claunia commented 2026-01-31 03:33:59 +00:00
Author
Owner
Copy Link

@tsukumijima commented on GitHub (Jun 8, 2021):

As you can see at https://github.com/PowerShell/PowerShell/issues/14949, this issue is

  • PSReadline is enabled
  • Using Windows Terminal

It only happens if. It happens in both Windows PowerShell 5.1 and PowerShell 7.

On the other hand, as a similar problem, if you enter a path that includes Japanese Full-width Midpoint (・), Midpoint will be dropped. This happens with Windows PowerShell 5.1, PowerShell 7, and even without Windows Terminal.

In either case, you can run Remove-Module PSReadLine to disable PSReadLine and the characters will be typed in without omissions. From this, I think it is certain that the bug in PSReadLine has an effect.

Various sites in Japan have suggested that the solution is to set Remove-Module PSReadLine in the profile to disable his PSReadLine.
PSReadLine provides beautiful highlights, so it's a shame that the Japanese need to disable it just for this bug.

I'm not sure if this issue is also caused by Windows Terminal, but I don't think it's preferable that it hasn't been resolved for years, so I think some action should be taken. This problem is fatal.

I'm using translation. The sentence may be unnatural.

@tsukumijima commented on GitHub (Jun 8, 2021): As you can see at https://github.com/PowerShell/PowerShell/issues/14949, this issue is - PSReadline is enabled - Using Windows Terminal It only happens if. It happens in both Windows PowerShell 5.1 and PowerShell 7. On the other hand, as a similar problem, if you enter a path that includes Japanese Full-width Midpoint (・), Midpoint will be dropped. This happens with Windows PowerShell 5.1, PowerShell 7, and even without Windows Terminal. In either case, you can run `Remove-Module PSReadLine` to disable PSReadLine and the characters will be typed in without omissions. From this, I think it is certain that the bug in PSReadLine has an effect. Various sites in Japan have suggested that the solution is to set `Remove-Module PSReadLine` in the profile to disable his PSReadLine. PSReadLine provides beautiful highlights, so it's a shame that the Japanese need to disable it just for this bug. I'm not sure if this issue is also caused by Windows Terminal, but I don't think it's preferable that it hasn't been resolved for years, so I think some action should be taken. This problem is fatal. I'm using translation. The sentence may be unnatural.
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 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#13102
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?