starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

keep the same path after switching from powershell to command prompt #15903

New Issue
Closed
opened 2026-01-31 04:51:46 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 04:51:46 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Nov 17, 2021).

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

Originally created by @ghost on GitHub (Nov 17, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> 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
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:51:46 +00:00
claunia commented 2026-01-31 04:51:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 17, 2021):

Amassing notes here before the end of the day:

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

@zadjii-msft commented on GitHub (Nov 17, 2021): Amassing notes here before the end of the day: * https://github.com/microsoft/terminal/issues/3158#issuecomment-764003033 * #10940 * #8933 * #9991 * #10614 * https://github.com/microsoft/terminal/issues/10105#issuecomment-842231981 I'll come through and turn that into an actual reply tomorrow morning
claunia commented 2026-01-31 04:51:48 +00:00
Author
Owner
Copy Link

@aungthanlwin commented on GitHub (Nov 17, 2021):

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 ."

@aungthanlwin commented on GitHub (Nov 17, 2021): 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 ."
claunia commented 2026-01-31 04:51:48 +00:00
Author
Owner
Copy Link

@jthoward64 commented on GitHub (Nov 19, 2021):

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

@jthoward64 commented on GitHub (Nov 19, 2021): > 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
claunia commented 2026-01-31 04:51:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 23, 2021):

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.

@zadjii-msft commented on GitHub (Nov 23, 2021): 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](https://github.com/MicrosoftDocs/terminal/pull/449/files) 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.
claunia commented 2026-01-31 04:51:48 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 24, 2021):

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

@ghost commented on GitHub (Nov 24, 2021): > 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](https://github.com/MicrosoftDocs/terminal/pull/449/files) 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
claunia commented 2026-01-31 04:51:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 24, 2021):

Awesome, thanks!

/dup #10232

@zadjii-msft commented on GitHub (Nov 24, 2021): Awesome, thanks! /dup #10232
claunia commented 2026-01-31 04:51:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 24, 2021):

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!

@ghost commented on GitHub (Nov 24, 2021): 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15903
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?