New tab doesn't inherit working directory for -d

[QuAzI]

Windows Terminal version

1.22.10352.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

Press Win+R
Execute wt -d c:\Projects to specify the folder that should be used as the starting directory for the console (according to documentation)
Open a new tab

Expected Behavior

For cases when wt -d used target directory should be inherited properly for new tabs and should be equal as the starting directory specified on console run

Actual Behavior

Currently, the path is C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.22.10352.0_x64__8wekyb3d8bbwe> instead of what you chose as the starting directory

[zadjii-msft]

Lemme at least cross link some thoughts here:

• New tabs don't launch in the directory of the first tab when launching WT via cmd.exe shorthand #14761
• 'Use parent process directory' not being respected for new Tabs #14817 (similar root cause, though that thread is very leveation specific)
• Other options for overriding profile starting directory #4637 IIRC is the thread where I was collecting all of these thoughts up

If I'm reading you right, you basically want to be able to have -d . apply to additional tabs created in that terminal window, not just the tab that wt -d . opens. I suspect that just using "Duplicate tab" rather than "Open new tab" will probably get you want you want here.

[QuAzI]

-d . means that I will use the current directory, not the starting directory. So, it's different.
At the same time, Duplicate tab starts with the starting directory, while I expected that it will inherit the current path too) And it absolutely doesn't work for different profiles, WSL for example

[quyenvsp]

same here, I remember it work before but not latest Terminal Preview version. Duplicate tab work but can not switch profile like from Git bash to CMD. new CMD tab will open system32 instead of Parent process directory

[DHowett]

This may have regressed in our windowing and remoting rewrite in #18215. Thanks!

[DHowett]

Actually, given that the original report is on 1.22 and @quyenvsp is talking about Preview... there may be two issues here.