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

Providing command-line arguments to a profile makes the terminal crash #13086

New Issue
Closed
opened 2026-01-31 03:33:26 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 03:33:26 +00:00
Owner
Copy Link

Originally created by @ClementNerma on GitHub (Mar 18, 2021).

Environment

Windows build number: 19042.868
Windows Terminal version (if applicable): 1.7.572.0

Steps to reproduce

wt -p "PowerShell" # Works

wt -p "PowerShell" pause # Closes immediatly
wt -p "PowerShell" -- pause # Same
wt -p "PowerShell" "-- pause" # Same

Expected behavior

The pause command provided to PowerShell should be executed normally, according to the documentation.

Actual behavior

The window closes immediatly if an additional argument is provided to the selected profile.

Originally created by @ClementNerma on GitHub (Mar 18, 2021). # Environment ```none Windows build number: 19042.868 Windows Terminal version (if applicable): 1.7.572.0 ``` # Steps to reproduce ```bash wt -p "PowerShell" # Works wt -p "PowerShell" pause # Closes immediatly wt -p "PowerShell" -- pause # Same wt -p "PowerShell" "-- pause" # Same ``` # Expected behavior The `pause` command provided to PowerShell should be executed normally, according to the documentation. # Actual behavior The window closes immediatly if an additional argument is provided to the selected profile.
claunia added the Resolution-Duplicate label 2026-01-31 03:33:26 +00:00
claunia commented 2026-01-31 03:33:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 18, 2021):

Interesting. Could you share your settings? I'm interested on the closeOnExit setting specifically - I'm betting that commandline isn't valid and the connection is closing immediately, which is causing the tab to close immediately, which is then closing the window.

@zadjii-msft commented on GitHub (Mar 18, 2021): Interesting. Could you share your settings? I'm interested on the `closeOnExit` setting specifically - I'm betting that commandline isn't valid and the connection is closing immediately, which is causing the tab to close immediately, which is then closing the window.
claunia commented 2026-01-31 03:33:28 +00:00
Author
Owner
Copy Link

@ClementNerma commented on GitHub (Mar 18, 2021):

Indeed, I set it to closeOnExit: "always". When I remove it, I get an error 0x80070002.

Seems like it's caused by the fact PowerShell cannot launch commands but only executables files directly. When I replace read with cmd.exe everything works fine.

Maybe there could be a quick mention in the docs?

EDIT : That being said running wt -p "<ProfileName>" works fine but wt -p "<ProfileName>" "binary" does not launch the binary inside the requested profile (I get the same error if I put /bin/ls with my WSL profile)

@ClementNerma commented on GitHub (Mar 18, 2021): Indeed, I set it to `closeOnExit: "always"`. When I remove it, I get an error `0x80070002`. Seems like it's caused by the fact PowerShell cannot launch commands but only executables files directly. When I replace `read` with `cmd.exe` everything works fine. Maybe there could be a quick mention in the docs? **EDIT :** That being said running `wt -p "<ProfileName>"` works fine but `wt -p "<ProfileName>" "binary"` does not launch the binary inside the requested profile (I get the same error if I put `/bin/ls` with my WSL profile)
claunia commented 2026-01-31 03:33:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 18, 2021):

So, this is more on Terminal’s side. We take the new commandline to be the path to an executable, plus its arguments to be run inside the terminal (incidentally, this is why /bin/ls isn’t valid). There isn’t currently a way to specify “run the thing identified by the profile, but tell it to run the following command”... because the way to do that differs between shells. I believe we have a workitem tracking this. We need to figure out a way to make this possible, as it keeps biting people.

@DHowett commented on GitHub (Mar 18, 2021): So, this is more on Terminal’s side. We take the new commandline to be _the path to an executable, plus its arguments_ to be run inside the terminal (incidentally, this is why /bin/ls isn’t valid). There isn’t currently a way to specify “run the thing identified by the profile, but tell it to run the following command”... because the way to do that differs between shells. I believe we have a workitem tracking this. We need to figure out a way to make this possible, as it keeps biting people.
claunia commented 2026-01-31 03:33:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 18, 2021):

(In effect, this replaces the PowerShell profile with one whose entire commandline is “pause”, instead of “powershell -c pause” or something.)

@DHowett commented on GitHub (Mar 18, 2021): (In effect, this replaces the PowerShell profile with one whose entire commandline is “pause”, instead of “powershell -c pause” or something.)
claunia commented 2026-01-31 03:33:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 18, 2021):

So the "Add support for appending a commandline to a profile's commandline" is trackeed over in #5528. I suppose this thread has generally become a duplicate of that discussion, so we can merge the two.

/dup #5528

@zadjii-msft commented on GitHub (Mar 18, 2021): So the "Add support for appending a commandline to a profile's commandline" is trackeed over in #5528. I suppose this thread has generally become a duplicate of that discussion, so we can merge the two. /dup #5528
claunia commented 2026-01-31 03:33:29 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 18, 2021):

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 (Mar 18, 2021): 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 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#13086
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?