keep the same path after switching from powershell to command prompt

[ghost]

Description of the new feature/enhancement

Proposed technical implementation details (optional)

When I open PowerShell by right-clicking in a folder, it opens in that path, but then when i switch to Command Prompt, it starts from User folder.

I want Windows Terminal to keep the same path after opening Command Prompt or other terminals from the tabs and not switch to their default path. so if i'm working with PowerShell in a specific directory and then open CMD from the same Terminal window, I want PowerShell to pass the current working directory to the CMD.

at least provide this as an option in Windows Terminal settings.

I'm using Windows 11 insider beta and the built-in Windows Terminal

Thanks

[zadjii-msft]

Amassing notes here before the end of the day:

• Open new terminal tab in same directory as existing tab (OSC 7?) #3158 (comment)
• open new tab not support use same cwd from start #10940
• "Open Windows Terminal here" does not continue to work for subsequent tabs, panes #8933
• Proposal: Evolution of startingDirectory #9991
• Opening new Terminal in same directory as current terminal #10614
• Duplicate the tab with the same path #10105 (comment)

I'll come through and turn that into an actual reply tomorrow morning

[aungthanlwin]

There is a workaround for this. You can use the -d option and "." (dot) notation to pass the current working directory to command prompt. For example, when you're in windows powershell, you can start command prompt with the command “wt -w 0 -p “Command Prompt” -d .” or "start cmd ."

[jthoward64]

There is a workaround for this. You can use the -d option and "." (dot) notation to pass the current working directory to command prompt. For example, when you're in windows powershell, you can start command prompt with the command “wt -w 0 -p “Command Prompt” -d .” or "start cmd ."

I think OP is referring to opening new profiles after running windows terminal from file explorer's context menu

[zadjii-msft]

Okay, so lemme get this stright

1. You right click in explorer (in c:\foo), and "open Windows Terminal here"
2. You get a PowerShell tab in c:\foo
3. You open a new Command Prompt tab, via the new tab menu or the command palette or whatever
4. it opens in whatever cmd.exe's startingDirectory is set to

and you want step 4 to open in c:\foo. Originally, I thought we were tracking this in #8933, but that only applied when the startingDirectory is set to ..

Now, I think you're going to have to do the OSC9;9 thing to emit the working directory, and then wait for #10232 to allow opening a tab/pane with the same directory, but a different profile.

Do I have that right? If so, I'm gonna call this one a duplicate of #10232.

[ghost]

Okay, so lemme get this stright

1. You right click in explorer (in c:\foo), and "open Windows Terminal here"
2. You get a PowerShell tab in c:\foo
3. You open a new Command Prompt tab, via the new tab menu or the command palette or whatever
4. it opens in whatever cmd.exe's startingDirectory is set to

and you want step 4 to open in c:\foo. Originally, I thought we were tracking this in #8933, but that only applied when the startingDirectory is set to ..

Now, I think you're going to have to do the OSC9;9 thing to emit the working directory, and then wait for #10232 to allow opening a tab/pane with the same directory, but a different profile.

Do I have that right? If so, I'm gonna call this one a duplicate of #10232.

Yes you got it right, I want it exactly like that.
thank you

[zadjii-msft]

Awesome, thanks!

/dup #10232

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!