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

Dragging or tabbing to a file with full-width chars in its filename causes caret be pushed way out of sync #10514

New Issue
Closed
opened 2026-01-31 02:23:41 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 02:23:41 +00:00
Owner
Copy Link

Originally created by @Masamune3210 on GitHub (Sep 6, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.450]
Windows Terminal version (if applicable): Tried on both 1.2.2381.0 and 1.3.2382.0

Any other software?

Steps to reproduce

  1. Name a file using full-width characters in its filename
  2. Attempt to either drag the file into the window or tab to the file while in the correct folder for auto-complete
  3. Notice that the caret gets pushed way off to the right, and stays that way for everything after the full-width chars

Not sure if its related to the full-width issue or not, but tabbing to the file also incorrectly escaped [ ] chars that were in the filename as well, adding a doublequote in front of each square bracket

Expected behavior

No cursor desync to occur, and correct handling of full-width chars

Actual behavior

Caret desync and improper special char escaping

Originally created by @Masamune3210 on GitHub (Sep 6, 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! --> <!-- 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: Microsoft Windows [Version 10.0.19041.450] Windows Terminal version (if applicable): Tried on both 1.2.2381.0 and 1.3.2382.0 Any other software? ``` # Steps to reproduce 1. Name a file using full-width characters in its filename 2. Attempt to either drag the file into the window or tab to the file while in the correct folder for auto-complete 3. Notice that the caret gets pushed way off to the right, and stays that way for everything after the full-width chars Not sure if its related to the full-width issue or not, but tabbing to the file also incorrectly escaped [ ] chars that were in the filename as well, adding a doublequote in front of each square bracket # Expected behavior No cursor desync to occur, and correct handling of full-width chars # Actual behavior Caret desync and improper special char escaping
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-31 02:23:41 +00:00
claunia commented 2026-01-31 02:23:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 6, 2020):

What shell are you using inside Terminal? The shell makes a huge difference here.

@DHowett commented on GitHub (Sep 6, 2020): _What shell are you using inside Terminal_? The shell makes a huge difference here.
claunia commented 2026-01-31 02:23:42 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Sep 6, 2020):

Sorry, didn't even think about that. It's PowerShell

@Masamune3210 commented on GitHub (Sep 6, 2020): Sorry, didn't even think about that. It's PowerShell
claunia commented 2026-01-31 02:23:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 9, 2020):

This is interesting!

It appears to be an issue in older versions of PSreadline, the line editing library in PowerShell.

image

image

It works fine with the version of PSReadline that comes with PowerShell 7, and it works fine without PSReadline.

The extra quote character comes from overzealous (but not incorrect!) escaping, and it should be fine.

It appears as though PSReadline does some codepage translation when it believes that the console cannot display fullwidth characters.

Here, I have changed the codepage to one that supports FW.

image

It now works.

Gonna close this one as external but fixed, since it is not a problem in newer versions of PowerShell.

Thanks!

/dup https://github.com/PowerShell/PSReadLine/issues/289

@DHowett commented on GitHub (Sep 9, 2020): This is interesting! It appears to be an issue in older versions of PSreadline, the line editing library in PowerShell. ![image](https://user-images.githubusercontent.com/189190/92540314-00c0af80-f1f9-11ea-99c2-8bb9ddb3c59d.png) ![image](https://user-images.githubusercontent.com/189190/92540328-0e763500-f1f9-11ea-82db-6d8a3255ce90.png) It works fine with the version of PSReadline that comes with PowerShell 7, and it works fine without PSReadline. The extra quote character comes from overzealous (but not incorrect!) escaping, and it should be fine. It appears as though PSReadline does some codepage translation when it believes that the console cannot display fullwidth characters. Here, I have changed the codepage to one that supports FW. ![image](https://user-images.githubusercontent.com/189190/92540416-5c8b3880-f1f9-11ea-9098-97863798452f.png) It now works. Gonna close this one as external but fixed, since it is not a problem in newer versions of PowerShell. Thanks! /dup https://github.com/PowerShell/PSReadLine/issues/289
claunia commented 2026-01-31 02:23:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 9, 2020):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Sep 9, 2020): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
claunia commented 2026-01-31 02:23:42 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Sep 9, 2020):

Is powershell updated externally? Always assumed it was updated as part of the OS? This issue occurs on latest stable of Win10

@Masamune3210 commented on GitHub (Sep 9, 2020): Is powershell updated externally? Always assumed it was updated as part of the OS? This issue occurs on latest stable of Win10
claunia commented 2026-01-31 02:23:43 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 9, 2020):

PowerShell 5.1, the version that comes with Windows, will not be updated any longer.

They have moved all of their effort to their new (well, it is years old by this point) open-source version that you can install from https://github.com/powershell/powershell.

@DHowett commented on GitHub (Sep 9, 2020): PowerShell 5.1, the version that comes with Windows, will not be updated any longer. They have moved all of their effort to their new (well, it is years old by this point) open-source version that you can install from https://github.com/powershell/powershell.
claunia commented 2026-01-31 02:23:43 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 9, 2020):

More info here: https://microsoft.com/PowerShell

@DHowett commented on GitHub (Sep 9, 2020): More info here: https://microsoft.com/PowerShell
claunia commented 2026-01-31 02:23:43 +00:00
Author
Owner
Copy Link

@Masamune3210 commented on GitHub (Sep 9, 2020):

Ok, thanks! Was unaware that the built-in version had been shuttled

@Masamune3210 commented on GitHub (Sep 9, 2020): Ok, thanks! Was unaware that the built-in version had been shuttled
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 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#10514
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?