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

Add the ability to use the command line arguments when opening a profile #10839

New Issue
Closed
opened 2026-01-31 02:31:39 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 02:31:39 +00:00
Owner
Copy Link

Originally created by @jmahlers on GitHub (Sep 30, 2020).

Description of the new feature/enhancement

Right now, in order to have the initial launch of windows terminal look like this:
wtscreenshot
where I have split screen at launch, first you have to pin a shortcut of windows terminal to the taskbar (Seperate issue of why does shift+rightclick perform differently for windows terminal compared to other apps). Like so:
wtshort
so that you can edit the target:
wttarget
with the target of:

C:\Users\Jeff\AppData\Local\Microsoft\WindowsApps\wt.exe -d C:\Starting\Dir; split-pane -p "Ubuntu-20.04"  -d C:\Starting\Dir

This is all overly complicated for the simple result and rather homebrew. For example, since I had to make a shortcut to the .exe to edit the target, the windows no longer nicely stack:
image

Rather than being built in functionality, this is just what I threw together after a bunch of tinkering.

Proposed technical implementation details (optional)

Have a setting for a profile where a user can tack on arguments to the launch of windows terminal. So that rather than doing the above, I could simply put

LaunchArguments: "-d C:\Starting\Dir; split-pane -p "Ubuntu-20.04"  -d C:\Starting\Dir"

or any other parameters into the setting json. This would unlock a lot of functionality for customizing how profiles appear at creation.

Originally created by @jmahlers on GitHub (Sep 30, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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). --> Right now, in order to have the initial launch of windows terminal look like this: ![wtscreenshot](https://user-images.githubusercontent.com/49463671/94651934-d8d7df80-02be-11eb-856b-a13f516e6df7.png) where I have split screen at launch, first you have to pin a shortcut of windows terminal to the taskbar (Seperate issue of why does shift+rightclick perform differently for windows terminal compared to other apps). Like so: ![wtshort](https://user-images.githubusercontent.com/49463671/94652320-73d0b980-02bf-11eb-9360-8f5b56b503a1.png) so that you can edit the target: ![wttarget](https://user-images.githubusercontent.com/49463671/94652412-9793ff80-02bf-11eb-8d14-3a709de1efbf.png) with the target of: ``` C:\Users\Jeff\AppData\Local\Microsoft\WindowsApps\wt.exe -d C:\Starting\Dir; split-pane -p "Ubuntu-20.04" -d C:\Starting\Dir ``` This is all overly complicated for the simple result and rather homebrew. For example, since I had to make a shortcut to the .exe to edit the target, the windows no longer nicely stack: ![image](https://user-images.githubusercontent.com/49463671/94652699-16893800-02c0-11eb-8908-6f2d5e6b373a.png) Rather than being built in functionality, this is just what I threw together after a bunch of tinkering. # Proposed technical implementation details (optional) Have a setting for a profile where a user can tack on arguments to the launch of windows terminal. So that rather than doing the above, I could simply put ``` LaunchArguments: "-d C:\Starting\Dir; split-pane -p "Ubuntu-20.04" -d C:\Starting\Dir" ``` or any other parameters into the setting json. This would unlock a lot of functionality for customizing how profiles appear at creation. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 02:31:39 +00:00
claunia commented 2026-01-31 02:31:41 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 1, 2020):

Thanks for the request! This sounds like an intersecting set with /dup #756, so I'm going to track it over there. They're pretty much the same thing, and we do have some ideas on how we'll tackle it. I don't blame you for not finding it, though. It's not particularly discoverable. 😄

@DHowett commented on GitHub (Oct 1, 2020): Thanks for the request! This sounds like an intersecting set with /dup #756, so I'm going to track it over there. They're pretty much the same thing, and we do have some ideas on how we'll tackle it. I don't blame you for not finding it, though. It's not particularly discoverable. :smile:
claunia commented 2026-01-31 02:31:41 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 1, 2020):

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 (Oct 1, 2020): 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!
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#10839
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?