Skip to content

WT can not "see" directories/env variables starting with capital letters #18776

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
endlessterror opened this issue Apr 9, 2025 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@endlessterror
Copy link

Windows Terminal version

1.22.10731.0

Windows build number

10.0.19045.5608

Other Software

No response

Steps to reproduce

Scenario 1

  1. Create a directory Εκλογές at C:\
  2. Try to tab complete writing for example cd \Ε followed by tab, where 'E' is the capital greek letter epsilon

Scenario 2
In scenario 2I'm trying to print the content of environment variable $Env:ALLUSERSPROFILE.
1, With a terminal open (set to powershell) press $ followed by english capital letter E

Expected Behavior

Scenario 1
Tab should auto-complete c:\E το c:\Εκλογές

Scenario 2
Pressing $ produces the character on screen, pressing capital E produces E

Actual Behavior

Scenario 1
Nothing happens nothing is printed

Scenario 2
Pressing $ produces the character on screen, pressing capital E produces nothing. If small e is pressed it is shown just fine.

@endlessterror endlessterror added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Apr 9, 2025
@DHowett
Copy link
Member

DHowett commented Apr 9, 2025

Thanks for the report!

Scenario 1 - it looks like E and Ε are different characters!

$ "EΕ" -split "" | % { "0x{0:X}" -f [int]$_[0] }
0x45
0x395

Are you sure you're entering the same one?

Does this work if you run PowerShell outside of Windows Terminal?

Scenario 2 -

Can you capture an input trace using the debug tap for Scenario 2/?

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Apr 9, 2025
@endlessterror
Copy link
Author

Hmm, I could not replicate scenario 2, perhaps I was trying with Greek caps?

I've made a debug tap on scenario 1, whereas I'm trying to mkdir \Ε (capital Greek epsilon). This does not work so I'm pressing ε (small Epsilon). Don't know how I'm supposed to upload the tap though, hope copying and pasting to a text file does the trick.

debug_tap.txt

Image

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Apr 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants