Open NewtonChutney opened 9 months ago
Okay, so this isn't shell integration related. I bet this regressed in 1.18. We probably still need to initially seed the TermControl's CWD with the "virtual cwd" we used at the time we created that control, ala #15280
(you could probably work around this today by having your shell manually tell the Terminal about the CWD: https://learn.microsoft.com/en-us/windows/terminal/tutorials/new-tab-same-directory)
Okay, so this isn't shell integration related. I bet this regressed in 1.18. We probably still need to initially seed the TermControl's CWD with the "virtual cwd" we used at the time we created that control, ala #15280
(you could probably work around this today by having your shell manually tell the Terminal about the CWD: https://learn.microsoft.com/en-us/windows/terminal/tutorials/new-tab-same-directory)
Maybe this is related to the “issue reappears after update 1.18” that occurred in #15173 ?
Windows Terminal version
1.18.3181.0
Windows build number
10.0.22631.2861
Other Software
No response
Steps to reproduce
Expected Behavior
The respawned process should have the same environment as the original process.
Actual Behavior
The respawned process launches with the default launch directory of WT,
C:\WINDOWS\system32>
https://github.com/microsoft/terminal/assets/70827815/3923ba36-08f6-4b8d-ba21-bd8ce1a5b227