starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"Use parent process directory" flag being ignored in some cases #19130

New Issue
Open
opened 2026-01-31 06:34:37 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:34:37 +00:00
Owner
Copy Link

Originally created by @brupelo on GitHub (Dec 24, 2022).

Windows Terminal version

1.15.3465.0

Windows build number

Microsoft Windows [Version 10.0.19045.2364]

Other Software

No response

Steps to reproduce

1.- Go to settings and modify the "Command Prompt" profile and enable the checkbox "Use parent process directory" in the Starting directory section
2.- Make sure "Command Prompt" profile will be used when using new-tab, new-windows and split-pane commands
3.- Create a new window using wt --startingDirectory d:\ , the new terminal will open on that directory
4.- Spawn a new-tab action (+ sign or shortcut) and the new tab will be using --startingDirectory c:\users\my_user . It happens the same if i try to split-pane or new-window commands

Expected Behavior

What I'd like to achieve is, each time I'm on a certain directory of my tab, opening a new tab/pane/window using the same directory of the source tab

For instance, in conemu this works wonderfully, each time i split panes it will use the current directory of the source pane.

Actual Behavior

When you run a new-window/new-tab/split-pane command from a tab with current directory A it will be using directory B.

Is this expected? I don't understand, what does it mean "Use parent process directory" then? Is this a bug?

Originally created by @brupelo on GitHub (Dec 24, 2022). ### Windows Terminal version 1.15.3465.0 ### Windows build number Microsoft Windows [Version 10.0.19045.2364] ### Other Software _No response_ ### Steps to reproduce 1.- Go to settings and modify the "Command Prompt" profile and enable the checkbox "Use parent process directory" in the Starting directory section 2.- Make sure "Command Prompt" profile will be used when using new-tab, new-windows and split-pane commands 3.- Create a new window using `wt --startingDirectory d:\` , the new terminal will open on that directory 4.- Spawn a new-tab action (+ sign or shortcut) and the new tab will be using --startingDirectory `c:\users\my_user` . It happens the same if i try to split-pane or new-window commands ### Expected Behavior What I'd like to achieve is, each time I'm on a certain directory of my tab, opening a new tab/pane/window using the same directory of the source tab For instance, in conemu this works wonderfully, each time i split panes it will use the current directory of the source pane. ### Actual Behavior When you run a new-window/new-tab/split-pane command from a tab with current directory A it will be using directory B. Is this expected? I don't understand, what does it mean "Use parent process directory" then? Is this a bug?
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 06:34:38 +00:00
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-Bug Needs-Triage
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#19130
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?