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

Issue with Non-interactive Behavior of Command Execution in Multi-tab Setup #21417

New Issue
Closed
opened 2026-01-31 07:44:05 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 07:44:05 +00:00
Owner
Copy Link

Originally created by @brupelo on GitHub (Mar 18, 2024).

Windows Terminal version

1.19.231113002-preview

Windows build number

Microsoft Windows [Version 10.0.19045.4170]

Other Software

No response

Steps to reproduce

Consider below run.cmd:

set COMMAND=cmd /k "vd && va venv && cls && python setup.py start"

wt -w %~n0 ^
nt --title="svc1:5000" --startingDirectory=%svc1% %COMMAND% ; ^
nt --title="svc2:5001" --startingDirectory=%svc2% %COMMAND% ; ^
nt --title="svc3:5002" --startingDirectory=%svc3% %COMMAND% ;
nt --title="svc4:5004" --startingDirectory=%svc4% %COMMAND%

I am writing to bring to your attention an issue I encountered while using a script to spin up multiple tabs in the terminal for running Python microservices.

The script I am utilizing successfully spins up multiple tabs, each intended to enable a virtual environment and launch a local server for a Python microservice. However, upon closer inspection, I noticed that the commands within each tab are not executed immediately upon opening the tab. Instead, they execute only when I manually click on each tab. This behavior suggests that the processes are non-interactive, which is not the desired functionality.

Could you please guide me on what might be causing this issue? I am eager to ensure that the script functions as intended, allowing for the automated deployment of the microservices without any delays or manual input.

Any insights or suggestions you can provide would be greatly appreciated.

Thank you for your attention to this matter.

Expected Behavior

Ideally, I would like the commands within each tab to start executing immediately upon opening, without requiring any manual intervention. This would ensure that the microservices are up and running seamlessly without any human interaction.

Actual Behavior

The commands within each tab are not executed immediately upon opening the tab

Originally created by @brupelo on GitHub (Mar 18, 2024). ### Windows Terminal version 1.19.231113002-preview ### Windows build number Microsoft Windows [Version 10.0.19045.4170] ### Other Software _No response_ ### Steps to reproduce Consider below run.cmd: ``` set COMMAND=cmd /k "vd && va venv && cls && python setup.py start" wt -w %~n0 ^ nt --title="svc1:5000" --startingDirectory=%svc1% %COMMAND% ; ^ nt --title="svc2:5001" --startingDirectory=%svc2% %COMMAND% ; ^ nt --title="svc3:5002" --startingDirectory=%svc3% %COMMAND% ; nt --title="svc4:5004" --startingDirectory=%svc4% %COMMAND% ``` I am writing to bring to your attention an issue I encountered while using a script to spin up multiple tabs in the terminal for running Python microservices. The script I am utilizing successfully spins up multiple tabs, each intended to enable a virtual environment and launch a local server for a Python microservice. However, upon closer inspection, I noticed that the commands within each tab are not executed immediately upon opening the tab. Instead, they execute only when I manually click on each tab. This behavior suggests that the processes are non-interactive, which is not the desired functionality. Could you please guide me on what might be causing this issue? I am eager to ensure that the script functions as intended, allowing for the automated deployment of the microservices without any delays or manual input. Any insights or suggestions you can provide would be greatly appreciated. Thank you for your attention to this matter. ### Expected Behavior Ideally, I would like the commands within each tab to start executing immediately upon opening, without requiring any manual intervention. This would ensure that the microservices are up and running seamlessly without any human interaction. ### Actual Behavior The commands within each tab are not executed immediately upon opening the tab
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:44:05 +00:00
claunia commented 2026-01-31 07:44:07 +00:00
Author
Owner
Copy Link

@brupelo commented on GitHub (Mar 18, 2024):

The simpler way to check this one would be using some sysadmin tool such as https://www.nirsoft.net/utils/cports.html or https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer . You can see how processes won't not forked until you click the tabs

@brupelo commented on GitHub (Mar 18, 2024): The simpler way to check this one would be using some sysadmin tool such as https://www.nirsoft.net/utils/cports.html or https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer . You can see how processes won't not forked until you click the tabs
claunia commented 2026-01-31 07:44:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 20, 2024):

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #13136 for more discussion.

/dup #13136

@zadjii-msft commented on GitHub (Mar 20, 2024): Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #13136 for more discussion. /dup #13136
claunia commented 2026-01-31 07:44:07 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Mar 20, 2024):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Mar 20, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 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#21417
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?