microsoft / microsoft/terminal

'Use parent process directory' not being respected for new Tabs

Open
#14,817 7 comments 9 reactions 0 assignees View on GitHub
Area-UserInterface Help Wanted Issue-Bug Priority-3 Product-Terminal
Dominant language
C++
Stars
105k
Forks
9.6k
Avg merge
3d 17h
Merged PRs (30d)
29

Description

### Windows Terminal version

1.16.10262.0

### Windows build number

10.0.2621.1105

### Other Software

_No response_

### Steps to reproduce

I have my WT setup so my default profile is lauch as admin and with the 'Use parent process directory' checked for starting directory. I then have all my other profiles set to 'Use parent process directory' for starting directory as well.

1. Use the context menu to launch Windows Terminal from a folder.
2. WT will launch default profile in the directory of the folder it was launch
3. Opening a new Tab launches the new profile to the 'C:\Windows\System32' folder

### Expected Behavior

Each new tab opened with different profiles should open in the same directory that WT was launched from

### Actual Behavior

Each new tab is launch to the 'C:\Windows\System32' folder.

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue using the listed steps: launch Windows Terminal from a folder, then open a new tab with another profile. Trace the profile starting-directory handling for newly opened tabs. Done means each profile opened in a new tab preserves the directory from which Windows Terminal was launched rather than using C:\Windows\System32.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.