microsoft/Terminal

Settings UI: Check that the starting directory is normalized

Open

#15,093 opened on Apr 3, 2023

View on GitHub
 (13 comments) (0 reactions) (0 assignees)C++ (3,212 forks)batch import
Area-TerminalConnectionHelp WantedIssue-BugProduct-Terminal

Repository metrics

Stars
 (35,764 stars)
PR merge metrics
 (Avg merge 27d 19h) (24 merged PRs in 30d)

Description

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)
  • 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 :) )

Contributor guide