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

Add send-input as Command-Line Argument #16774

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

Originally created by @joswr1ght on GitHub (Feb 14, 2022).

Description of the new feature/enhancement

Without specifying a custom profile, it is not possible to send a startup command in the default pane when starting Windows terminal. While the Windows Terminal command-line argument split-pane accepts a commandline argument to run a command, the default pane cannot run a command unless it is specified in the profile. This limits the flexibility of starting Windows Terminal with specific configurations defined at the command line.

For example, I can use command line arguments to customize panes and change the focus pane:

wt -M split-pane -s 0.1 -H -p "Command Prompt" ping -t www.google.com ; move-focus up ; split-pane -s 0.85 -H -p "Windows PowerShell"

Capture

The combination of split-pane and move-focus allows for tremendous flexibility in creating specific layouts for tasks. However, the default pane (top most in this screenshot) cannot accept a command line or any other input. The new panes through split-pane can accept input as a command-line argument, but the top-most pane cannot.

Proposed technical implementation details (optional)

Adding send-input as a command-line argument allows the user to have great flexibility in how commands are sent to different panes. Using move-focus, the user can send input into any pane to run startup commands as needed to meet specific Windows Terminal startup requirements.

With send-input as a command-line argument, the default pane could accept commands and other input without changing the Windows Terminal profile settings:

wt -M split-pane -s 0.1 -H -p "Command Prompt" ping -t www.google.com ; move-focus up ; split-pane -s 0.85 -H -p "Windows PowerShell" ; move-focus up ; send-input ping www.microsoft.com

Submitted for your review, thank you!

Originally created by @joswr1ght on GitHub (Feb 14, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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). --> Without specifying a custom profile, it is not possible to send a startup command in the default pane when starting Windows terminal. While the Windows Terminal command-line argument `split-pane` accepts a `commandline` argument to run a command, the default pane cannot run a command unless it is specified in the profile. This limits the flexibility of starting Windows Terminal with specific configurations defined at the command line. For example, I can use command line arguments to customize panes and change the focus pane: ``` wt -M split-pane -s 0.1 -H -p "Command Prompt" ping -t www.google.com ; move-focus up ; split-pane -s 0.85 -H -p "Windows PowerShell" ``` ![Capture](https://user-images.githubusercontent.com/1318817/153871848-c1fb9f38-adef-41ea-babc-0e68b39e23ac.PNG) The combination of `split-pane` and `move-focus` allows for tremendous flexibility in creating specific layouts for tasks. However, the default pane (top most in this screenshot) cannot accept a command line or any other input. The new panes through `split-pane` can accept input as a command-line argument, but the top-most pane cannot. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> Adding `send-input` as a command-line argument allows the user to have great flexibility in how commands are sent to different panes. Using `move-focus`, the user can send input into any pane to run startup commands as needed to meet specific Windows Terminal startup requirements. With `send-input` as a command-line argument, the default pane could accept commands and other input without changing the Windows Terminal profile settings: ``` wt -M split-pane -s 0.1 -H -p "Command Prompt" ping -t www.google.com ; move-focus up ; split-pane -s 0.85 -H -p "Windows PowerShell" ; move-focus up ; send-input ping www.microsoft.com ``` Submitted for your review, thank you!
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 05:22:26 +00:00
claunia commented 2026-01-31 05:22:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 14, 2022):

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

/dup #9368

@zadjii-msft commented on GitHub (Feb 14, 2022): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #9368 for more discussion. /dup #9368
claunia commented 2026-01-31 05:22:27 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 14, 2022):

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 (Feb 14, 2022): 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!
claunia commented 2026-01-31 05:22:28 +00:00
Author
Owner
Copy Link

@joswr1ght commented on GitHub (Feb 14, 2022):

Thank you @zadjii-msft !

@joswr1ght commented on GitHub (Feb 14, 2022): Thank you @zadjii-msft !
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#16774
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?