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

[Question] How to send command line to the console of a profile #20577

New Issue
Closed
opened 2026-01-31 07:18:09 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 07:18:09 +00:00
Owner
Copy Link

Originally created by @htcfreek on GitHub (Sep 29, 2023).

Description of the new feature/enhancement

How can I start WT with a specified profile and send arguments to the console of this profile (e.g. use Powershell profile and ping host).

I tired wt.exe new-tab -p "Powershell" -c "Get-Services" which results in an error message:

[Fehler 2147942402 (0x80070002) beim Start von `{Get-Services}']

xref: https://learn.microsoft.com/de-de/windows/terminal/command-line-arguments?tabs=windows#passing-an-argument-to-the-default-shell

Proposed technical implementation details (optional)

Originally created by @htcfreek on GitHub (Sep 29, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 How can I start WT with a specified profile and send arguments to the console of this profile (e.g. use Powershell profile and ping host). I tired `wt.exe new-tab -p "Powershell" -c "Get-Services"` which results in an error message: ``` [Fehler 2147942402 (0x80070002) beim Start von `{Get-Services}'] ``` xref: https://learn.microsoft.com/de-de/windows/terminal/command-line-arguments?tabs=windows#passing-an-argument-to-the-default-shell # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia commented 2026-01-31 07:18:13 +00:00
Author
Owner
Copy Link

@htcfreek commented on GitHub (Sep 29, 2023):

@zadjii-msft
Is the problem I described a bug or simply not implemented?

@htcfreek commented on GitHub (Sep 29, 2023): @zadjii-msft Is the problem I described a bug or simply not implemented?
claunia commented 2026-01-31 07:18:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 29, 2023):

Oh, I think you're just doing it wrong here. I suspect what you're trying to do is the --appendCommandline thing, from #5528 / #15822.

When you call wt -p "PowerShell" -c Get-Services, wt treats -c Get-Services as the command parameter, and replaces your PowerShell profile's commandline with that. And CreateProcess("-c Get-Services",...) clearly doesn't work 😝

So, you'll either want

  • wt -p PowerShell -- {path to powershell} -c Get-Services
  • wt -p PowerShell --appendCommandline -- -c Get-Services (starting in v1.19)
@zadjii-msft commented on GitHub (Sep 29, 2023): Oh, I think you're just doing it wrong here. I _suspect_ what you're trying to do is the `--appendCommandline` thing, from #5528 / #15822. When you call `wt -p "PowerShell" -c Get-Services`, `wt` treats `-c Get-Services` as the `command` parameter, and _replaces_ your PowerShell profile's `commandline` with that. And `CreateProcess("-c Get-Services",...)` clearly doesn't work 😝 So, you'll either want * `wt -p PowerShell -- {path to powershell} -c Get-Services` * `wt -p PowerShell --appendCommandline -- -c Get-Services` (starting in v1.19)
claunia commented 2026-01-31 07:18:13 +00:00
Author
Owner
Copy Link

@htcfreek commented on GitHub (Sep 29, 2023):

So, you'll either want wt -p PowerShell -- {path to powershell} -c Get-Services

@zadjii-msft
Does {path to powershell} respect the path variable? Or do I need to specify the full path?

@htcfreek commented on GitHub (Sep 29, 2023): > So, you'll either want `wt -p PowerShell -- {path to powershell} -c Get-Services` @zadjii-msft Does `{path to powershell}` respect the path variable? Or do I need to specify the full path?
claunia commented 2026-01-31 07:18:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 29, 2023):

Typically, yes, it'll respect the PATH. If you're just doing simple scripting, that's usually fine, though, BEST PRACTICE would be to specify the full path.

@zadjii-msft commented on GitHub (Sep 29, 2023): Typically, yes, it'll respect the `PATH`. If you're just doing simple scripting, that's usually fine, though, BEST PRACTICE would be to specify the full path.
claunia commented 2026-01-31 07:18:14 +00:00
Author
Owner
Copy Link

@htcfreek commented on GitHub (Oct 2, 2023):

@zadjii-msft
Thank you for your help. I think this is what I need.
Unfortunately I can't test the v1.19 command line because wt.exe entered in run dialog brings me an access denied error.

@htcfreek commented on GitHub (Oct 2, 2023): @zadjii-msft Thank you for your help. I think this is what I need. Unfortunately I can't test the v1.19 command line because `wt.exe` entered in run dialog brings me an `access denied` error.
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-Question Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-Answered
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#20577
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?