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

Feature Request: wt.exe to return PID of new child process on Standard Output #19460

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

Originally created by @martin-rueegg on GitHub (Feb 25, 2023).

Description of the new feature/enhancement

In some scenarios it is important to be able to store the PID of a newly created shell (to kill it or wait for its termination asynchronously, to name two).

When launching a new wt.exe instance in order to run a command in another tab or split-pane, the console is actually instantiated from the already running instance. Hence, the calling instance terminates and the new console is not a child of the invoking console.

While it makes no sense to keep all the WT instances alive, it would be great if the PID of the newly created console could be returned on standard output, upon request.

Proposed technical implementation details (optional)

Add an additional option that is used when launching a new command, console, tab, or pane, e.g. --return-pid that would return the PID of the invoked child process, if wt.exe terminates.

Originally created by @martin-rueegg on GitHub (Feb 25, 2023). # 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). --> In some scenarios it is important to be able to store the PID of a newly created shell (to kill it or wait for its termination asynchronously, to name two). When launching a new `wt.exe` instance in order to run a command in another tab or split-pane, the console is actually instantiated from the already running instance. Hence, the calling instance terminates and the new console is not a child of the invoking console. While it makes no sense to keep all the WT instances alive, it would be great if the PID of the newly created console could be returned on standard output, upon request. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> Add an additional option that is used when launching a new command, console, tab, or pane, e.g. `--return-pid` that would return the PID of the invoked child process, if `wt.exe` terminates.
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 Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-Won't-Fix
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#19460
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?