microsoft/Terminal
Vedi su GitHubSettings UI: Check that the starting directory is normalized
Open
#15.093 aperta il 3 apr 2023
Area-TerminalConnectionHelp WantedIssue-BugProduct-Terminal
Metriche repository
- Star
- (35.764 star)
- Metriche merge PR
- (Merge medio 27g 19h) (24 PR mergiate in 30 g)
Descrizione
Windows Terminal version
1.16.10262.0
Windows build number
10.0.22000.1696
Other Software
No response
Steps to reproduce
- create a new profile
- Command line - >
cmd.exe - "Starting directory" -? enter an existing path using a lower case drive letter (e.g.
c:\users)
- Command line - >
- start a new terminal session with the new profile
Expected Behavior
cmd.exe is started in C:\Users as drive letters are upper case and NTFS is by default case preserving.
in the case where NTFS was set to be case sensitive then I would expect cmd.exe to be started in C:\users as the drive letters are always case insensitive and canonically upper case.
Actual Behavior
the CWD is exactly as entered (all lower case)
This causes some subtle issues with some programs / developer environments where tests are asserting that some log was written containing a canonicalized path.
(also this is half way between an issue and a new feature :) )