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

Terminal changes C: to c: #21466

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

Originally created by @mikedice on GitHub (Apr 1, 2024).

Windows Terminal version

1.19.10573.0

Windows build number

Microsoft Windows [Version 10.0.22631.3296]

Other Software

Visual Studio 2022 Developer Command Prompt v17.9.3

Steps to reproduce

Just open the VS2022 Command prompt in terminal. I see, the root of the C drive (the only drive on the computer) is lower case 'c:' instead of uppercase 'C:'. This breaks an important script used by my team for website development. I have a bug for the JS package filed too here: https://github.com/vitejs/vite/issues/16324

While I understand that changing the case of the root of the drive is not technically wrong on Windows since c:\ and C:\ represent the same thing, it should be avoided if possible because some tools and scripts like Vite will be sensitive to that kind of change. What is the reason for the case change? Can it be avoided?

Expected Behavior

Use the casing for the root drive that is assigned by the operating system.

Actual Behavior

Terminal does not use the casing for the root drive that is assigned by the operating system and this can break tools that are sensitive to such changes.

Originally created by @mikedice on GitHub (Apr 1, 2024). ### Windows Terminal version 1.19.10573.0 ### Windows build number Microsoft Windows [Version 10.0.22631.3296] ### Other Software Visual Studio 2022 Developer Command Prompt v17.9.3 ### Steps to reproduce Just open the VS2022 Command prompt in terminal. I see, the root of the C drive (the only drive on the computer) is lower case 'c:\' instead of uppercase 'C:\'. This breaks an important script used by my team for website development. I have a bug for the JS package filed too here: https://github.com/vitejs/vite/issues/16324 While I understand that changing the case of the root of the drive is not technically wrong on Windows since c:\ and C:\ represent the same thing, it should be avoided if possible because some tools and scripts like Vite will be sensitive to that kind of change. What is the reason for the case change? Can it be avoided? ### Expected Behavior Use the casing for the root drive that is assigned by the operating system. ### Actual Behavior Terminal does not use the casing for the root drive that is assigned by the operating system and this can break tools that are sensitive to such changes.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:45:34 +00:00
claunia commented 2026-01-31 07:45:35 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 1, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (Apr 1, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Open similar issues: - [Settings UI: Check that the starting directory is normalized (#15093)](https://github.com/microsoft/terminal/issues/15093), similarity score: 0.76 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:45:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 1, 2024):

  • Does this repro if the vintage "Windows Console Host" is set as your default terminal in the settings app?
  • In a VS prompt, what is the output of set HOMEDRIVE & set SystemDrive?
  • Same question, but in a normal CMD tab?
  • Does anything look askew (DHowett EDIT: it said eschew) in the Environment Variables settings dialog/?
@zadjii-msft commented on GitHub (Apr 1, 2024): * Does this repro if the vintage "Windows Console Host" is set as your default terminal in the settings app? * In a VS prompt, what is the output of `set HOMEDRIVE & set SystemDrive`? * Same question, but in a normal CMD tab? * Does anything look askew (DHowett EDIT: it said `eschew`) in the Environment Variables settings dialog/?
claunia commented 2026-01-31 07:45:35 +00:00
Author
Owner
Copy Link

@mikedice commented on GitHub (Apr 1, 2024):

In my Terminal app Windows Console Host is set as the Default Terminal Application

From VS2022 Command prompt in Terminal
c:\Users\mikedice\source\repos>set HOMEDRIVE
HOMEDRIVE=C:

c:\Users\mikedice\source\repos>set SystemDrive
SystemDrive=C:

From classic command prompt
C:\Users\mikedice>set systemdrive
SystemDrive=C:

C:\Users\mikedice>set homedrive
HOMEDRIVE=C:

I dumped all environment variables and I do see this:
VSCMD_START_DIR=c:\users\mikedice\source\repos
In fact this is the only place lower case c: is shown

And then I saw that VSCMD_START_DIR=c:\users\mikedice\source\repos was set in the terminal Command Line property: cmd /k "set VSCMD_START_DIR=C:\users\mikedice\source\repos & "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\Tools\VsDevCmd.bat" -startdir=auto -arch=x64 -host_arch=x64"
I think I remember now setting that so the vsdevcmd prompt lands where i want it to and in that Command Line I used lower case c:

Guess this issue can be resolved by design

@mikedice commented on GitHub (Apr 1, 2024): In my Terminal app Windows Console Host is set as the Default Terminal Application From VS2022 Command prompt in Terminal c:\Users\mikedice\source\repos>set HOMEDRIVE HOMEDRIVE=C: c:\Users\mikedice\source\repos>set SystemDrive SystemDrive=C: From classic command prompt C:\Users\mikedice>set systemdrive SystemDrive=C: C:\Users\mikedice>set homedrive HOMEDRIVE=C: I dumped all environment variables and I do see this: VSCMD_START_DIR=c:\users\mikedice\source\repos In fact this is the only place lower case c: is shown And then I saw that VSCMD_START_DIR=c:\users\mikedice\source\repos was set in the terminal Command Line property: cmd /k "set VSCMD_START_DIR=C:\users\mikedice\source\repos & "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\Tools\VsDevCmd.bat" -startdir=auto -arch=x64 -host_arch=x64" I think I remember now setting that so the vsdevcmd prompt lands where i want it to and in that Command Line I used lower case c: Guess this issue can be resolved by design
claunia commented 2026-01-31 07:45:36 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 1, 2024):

Ah! Thanks for following up.

I usually work around this with the -SkipAutomaticLocation argument to Enter-VsDevShell or the -startdir=none argument to vsdevcmd. That puts Terminal in charge of the starting directory, so you can use the normal Starting Directory setting.

We haven't done this by default for consistency with the existing Developer Shell shortcuts in the start menu.

I'll close this one out! Thanks!

@DHowett commented on GitHub (Apr 1, 2024): Ah! Thanks for following up. I usually work around this with the `-SkipAutomaticLocation` argument to `Enter-VsDevShell` or the `-startdir=none` argument to vsdevcmd. That puts Terminal in charge of the starting directory, so you can use the normal Starting Directory setting. We haven't done this by default for consistency with the existing Developer Shell shortcuts in the start menu. I'll close this one out! Thanks!
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 Issue-Bug Needs-Attention Needs-Triage
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#21466
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?