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

Feature Request - commandline in json should support paths #2232

New Issue
Closed
opened 2026-01-30 22:50:09 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 22:50:09 +00:00
Owner
Copy Link

Originally created by @Karl-WE on GitHub (Jun 25, 2019).

Summary of the new feature/enhancement

currently profiles.json does not support paths for commandline

supported:
"commandline" : "pwsh.exe",
"commandline" : "cmd.exe",

not supported:
"commandline" : "C:\Program Files\PowerShell\6-preview\pwsh.exe",

This scenario expects the following:
the *.exe is available through system env path $env:path
the *.exe name is unique

Proposed technical implementation details (optional)

please support absolute or relative paths / paths with environment variables like %appdata% or $env:appdata (don't know if this PoSh variable can be used outside PoSh) so better rely on legacy OS variables.

Originally created by @Karl-WE on GitHub (Jun 25, 2019). # Summary of the new feature/enhancement currently profiles.json does not support paths for commandline supported: "commandline" : "pwsh.exe", "commandline" : "cmd.exe", not supported: "commandline" : "C:\Program Files\PowerShell\6-preview\pwsh.exe", This scenario expects the following: the *.exe is available through system env path $env:path the *.exe name is unique # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> please support absolute or relative paths / paths with environment variables like %appdata% or $env:appdata (don't know if this PoSh variable can be used outside PoSh) so better rely on legacy OS variables.
claunia added the Issue-QuestionArea-SettingsResolution-AnsweredProduct-Terminal labels 2026-01-30 22:50:10 +00:00
claunia commented 2026-01-30 22:50:10 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 25, 2019):

"does not support"

did you try it?

@DHowett-MSFT commented on GitHub (Jun 25, 2019): "does not support" did you try it?
claunia commented 2026-01-30 22:50:11 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 25, 2019):

Probably Escaping Character Escaped your mind for a bit.
"C:\\Program Files\\PowerShell\\6-preview\\pwsh.exe"

@Shorotshishir commented on GitHub (Jun 25, 2019): Probably Escaping Character Escaped your mind for a bit. `"C:\\Program Files\\PowerShell\\6-preview\\pwsh.exe"`
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-Settings Issue-Question Product-Terminal 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#2232
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?