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

Add support for --file,-f configuration_file for reading a list of commands from a file #7542

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

Originally created by @zadjii-msft on GitHub (Apr 22, 2020).

From the original spec:

Run these commands in the given Windows Terminal session. Enables opening new
tabs in already running Windows Terminal windows. See Future
Considerations for more details.

Originally created by @zadjii-msft on GitHub (Apr 22, 2020). From the original spec: > Run these commands in the given Windows Terminal session. Enables opening new > tabs in already running Windows Terminal windows. See [Future > Considerations](#Future-Considerations) for more details.
claunia added the Issue-TaskProduct-TerminalArea-Commandline labels 2026-01-31 01:06:51 +00:00
claunia commented 2026-01-31 01:06:52 +00:00
Author
Owner
Copy Link

@driver1998 commented on GitHub (May 30, 2020):

I guess it might be better to be able to read commands from a pipe? So that we can
echo -p "Powershell"; split-pane -p "Ubuntu" | wt.exe

or
type commands.txt | wt.exe

or even
some_launcher | wt.exe
when some_launcher splits the commands?

@driver1998 commented on GitHub (May 30, 2020): I guess it might be better to be able to read commands from a pipe? So that we can echo -p "Powershell"; split-pane -p "Ubuntu" | wt.exe or type commands.txt | wt.exe or even some_launcher | wt.exe when some_launcher splits the commands?
claunia commented 2026-01-31 01:06:52 +00:00
Author
Owner
Copy Link

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

From #12583:

There is "persisted window layout" and there are subcommands (sp) to start a new windows with some layout. However, it's not really easy to have a new window with a specific layout.

This feature request asks to load some layout definition file like this (from zellij.dev/documentation/layouts.html):

tabs:
  - direction: Vertical
    parts:
      - direction: Horizontal
        parts:
          - direction: Vertical
          - direction: Vertical
      - direction: Horizontal

for instance via wt -layout preset.yaml. The preset file can be enhanced further with profile name to load, starting directory, or even with a start command (eg, launch some additional task).

This raises the good point - we might want it to be something like a list of actions to perform. We already serialize the window state to JSON, so why can't we just parse a list of actions from a JSON file to execute. This might be more flexible than just a list of subcommands, with the caveat that now all actions need to be able to work before the terminal window is created, not just the few known well-behaving subcommands.

@zadjii-msft commented on GitHub (Feb 25, 2022): From #12583: > There is "persisted window layout" and there are subcommands (sp) to start a new windows with some layout. However, it's not really easy to have a new window with a specific layout. > > This feature request asks to load some layout definition file like this (from [zellij.dev/documentation/layouts.html](https://zellij.dev/documentation/layouts.html)): > > ``` > tabs: > - direction: Vertical > parts: > - direction: Horizontal > parts: > - direction: Vertical > - direction: Vertical > - direction: Horizontal > ``` > > for instance via `wt -layout preset.yaml`. The preset file can be enhanced further with profile name to load, starting directory, or even with a start command (eg, launch some additional task). This raises the good point - we might want it to be something like a list of actions to perform. We already serialize the window state to JSON, so why can't we just parse a list of actions from a JSON file to execute. This might be _more_ flexible than just a list of subcommands, with the caveat that now _all_ actions need to be able to work before the terminal window is created, not just the few known well-behaving subcommands.
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 Area-Commandline Issue-Task Product-Terminal
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#7542
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?