Skip to content

Launching with --startingDirectory does not work for "." in v1.23 - affects VSCode #18540

@rkodey

Description

@rkodey

Windows Terminal version

1.23.10353.0

Windows build number

10.0.19045.5371

Other Software

  • Windows Terminal in portable mode using ".portable"
  • This bug affects VSCode, when it launches the external terminal.
    • But, VSCode is not required, as shown below

Steps to reproduce

See basic configuration settings.json in comment below
Open a command prompt

cd \Users

Expected Behavior

Version 1.22.10352.0 works as expected.

cd \Users
command-line Opens Terminal In
wt.exe C:\Users
wt.exe -d . C:\Users
wt.exe -d "." C:\Users
wt.exe -d "C:\Users" C:\Users
wt.exe --startingDirectory . C:\Users
wt.exe --startingDirectory "." C:\Users
wt.exe --startingDirectory "C:\Users" C:\Users

Actual Behavior

Version 1.23.10353.0 shows the bug.

cd \Users
command-line Opens Terminal In
wt.exe C:\WINDOWS\system32
wt.exe -d . C:\WINDOWS\system32
wt.exe -d "." C:\WINDOWS\system32
wt.exe -d "C:\Users" C:\Users
wt.exe --startingDirectory . C:\WINDOWS\system32
wt.exe --startingDirectory "." C:\WINDOWS\system32
wt.exe --startingDirectory "C:\Users" C:\Users

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-BugIt either shouldn't be doing this or needs an investigation.Resolution-DuplicateThere's another issue on the tracker that's pretty much the same thing.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions