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

Default to pwsh.exe then powershell.exe for cli app profiles #13278

New Issue
Closed
opened 2026-01-31 03:38:30 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 03:38:30 +00:00
Owner
Copy Link

Originally created by @WSLUser on GitHub (Apr 1, 2021).

Description of the new feature/enhancement

If you create a custom profile for running a cli app such as the SSH profile, default to using pwsh.exe for running that cli app. If it's not installed, then default to powershell.exe.

Proposed technical implementation details (optional)

Looks like cli apps such as SSH are registered to CMD automatically by WIndows Terminal. So change this to powershell.exe instead and add logic to prioritize use of pwsh.exe if installed before attempting to use powershell.exe.

An aside: I notice defining powershell.exe in the commandline parameter works as expected. However setting pwsh.exe does not. It opens a tab and immediately closes and in the brief second it's open, you can notice an error about not recognizing ssh even though in a normal pwsh tab, ssh works just fine (you might need to flash the tab a few times to get enough of the error to read it, or better yet, use some screen recording software to capture it and simply review the recording). So likely there's some env var issues there on WT side (PS7 is at top of env vars with SSH right below it).

Originally created by @WSLUser on GitHub (Apr 1, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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). --> If you create a custom profile for running a cli app such as the SSH profile, default to using pwsh.exe for running that cli app. If it's not installed, then default to powershell.exe. # Proposed technical implementation details (optional) Looks like cli apps such as SSH are registered to CMD automatically by WIndows Terminal. So change this to powershell.exe instead and add logic to prioritize use of pwsh.exe if installed before attempting to use powershell.exe. <!-- A clear and concise description of what you want to happen. --> An aside: I notice defining powershell.exe in the commandline parameter works as expected. However setting pwsh.exe does not. It opens a tab and immediately closes and in the brief second it's open, you can notice an error about not recognizing ssh even though in a normal pwsh tab, ssh works just fine (you might need to flash the tab a few times to get enough of the error to read it, or better yet, use some screen recording software to capture it and simply review the recording). So likely there's some env var issues there on WT side (PS7 is at top of env vars with SSH right below it).
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 03:38:30 +00:00
claunia commented 2026-01-31 03:38:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 1, 2021):

Terminal does not launch CLI applications using another shell; it launches them directly using CreateProcess. I do not think that we should add powershell's start-up time to the start-up process for every profile; it would waste time and confer no benefit.

@DHowett commented on GitHub (Apr 1, 2021): Terminal does not launch CLI applications using another shell; it launches them directly using CreateProcess. I do not think that we should add powershell's start-up time to the start-up process for every profile; it would waste time and confer no benefit.
claunia commented 2026-01-31 03:38:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 1, 2021):

You can tell this by looking at Process Explorer -- the spawned CLI application has no parent process other than WindowsTerminal.exe. 😄

@DHowett commented on GitHub (Apr 1, 2021): You can tell this by looking at Process Explorer -- the spawned CLI application has no parent process other than WindowsTerminal.exe. :smile:
claunia commented 2026-01-31 03:38:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 1, 2021):

An aside: I notice defining powershell.exe in the commandline parameter works as expected. However setting pwsh.exe does not. It opens a tab and immediately closes and in the brief second it's open, you can notice an error about not recognizing ssh even though in a normal pwsh tab, ssh works just fine (you might need to flash the tab a few times to get enough of the error to read it, or better yet, use some screen recording software to capture it and simply review the recording). So likely there's some env var issues there on WT side (PS7 is at top of env vars with SSH right below it).

I would guess that you are using a 32-bit version of pwsh. If you leave 'closeOnExit' set to its default setting, you will get to see the error message.

@DHowett commented on GitHub (Apr 1, 2021): > An aside: I notice defining powershell.exe in the commandline parameter works as expected. However setting pwsh.exe does not. It opens a tab and immediately closes and in the brief second it's open, you can notice an error about not recognizing ssh even though in a normal pwsh tab, ssh works just fine (you might need to flash the tab a few times to get enough of the error to read it, or better yet, use some screen recording software to capture it and simply review the recording). So likely there's some env var issues there on WT side (PS7 is at top of env vars with SSH right below it). I would guess that you are using a 32-bit version of pwsh. If you leave 'closeOnExit' set to its default setting, you will get to see the error message.
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 Needs-Tag-Fix Needs-Triage
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#13278
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?