microsoft / microsoft/terminal
Ctrl or shift click the new tab button does not use the parent directory as working directory
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
### Windows Terminal version
1.21.2911.0
### Windows build number
10.0.19045.5011
### Other Software
_No response_
### Steps to reproduce
0. Set default profile CMD (or PS; but steps below are for CMD).
1. Set your CMD profile's "Starting directory" to "Use parent process directory".
3. Open a new window of WT at a non-default directory, say, `C:\files\`.
4. In this window, click the drop down button (V) next to new tab button (+), and shift or ctrl click the CMD option to create a new window or an administrator window.
5. Observe the new window is correctly using `C:\files\` as current working dir, as expected.
6. Back to the original window. Shift or ctrl click the new tab button (+) directly.
### Expected Behavior
It should create a new window or a new administrator window with default profile, which should be CMD, so it should create a window using `C:\files\` as starting dir just like step 4-5.
### Actual Behavior
It creates a window using `C:\WINDOWS\system32` as working dir, not parent process dir.
Contributor guide
Research direction
Start by reproducing the two launch paths in Windows Terminal 1.21.2911.0 with CMD configured to use the parent process directory, comparing the direct new-tab-button action with the dropdown CMD action. Done means Ctrl- or Shift-clicking the new tab button opens a new or elevated window in the parent directory instead of C:\WINDOWS\system32.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100