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

Hidden profiles cannot be specified with -p tag from command line. #11552

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

Originally created by @jmahlers on GitHub (Nov 23, 2020).

Environment

Microsoft Windows [Version 10.0.19042.630]
Windows Terminal
Version: 1.4.3243.0

WSL Ubuntu and others but not relevant.

Steps to reproduce

Create a profile for example:

{
                "guid": "{00000000-35be-5f56-a8ff-afceeeaa6101}",
                "name": "Command-Prompt-In-Place",
                "commandline": "cmd.exe",
                "startingDirectory": ".",
                "hidden": true
}

Then, attempt to create an instance of windows terminal from the command line with this profile ie:

wt.exe -p "Command-Prompt-In-Place"

Expected behavior

The specified profile should be chosen. This is useful so that a profile can be triggered by a command that isn't taking up space in the drop down in the app. One example is so that the default profile can start in some useful directory "C:\src" while an otherwise identical profile can start in ".". This is useful because then a profile can start in the current directory without taking up space in the menus. I am using this so I can right click and have "Open windows terminal here" in the context menu. Obviously the profile for "Open windows terminal here" is not needed in the menus.

Actual behavior

The hidden profile is not targetable and the default profile is chosen.

Originally created by @jmahlers on GitHub (Nov 23, 2020). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Microsoft Windows [Version 10.0.19042.630] Windows Terminal Version: 1.4.3243.0 WSL Ubuntu and others but not relevant. # Steps to reproduce <!-- A description of how to trigger this bug. --> Create a profile for example: ``` { "guid": "{00000000-35be-5f56-a8ff-afceeeaa6101}", "name": "Command-Prompt-In-Place", "commandline": "cmd.exe", "startingDirectory": ".", "hidden": true } ``` Then, attempt to create an instance of windows terminal from the command line with this profile ie: `wt.exe -p "Command-Prompt-In-Place"` # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The specified profile should be chosen. This is useful so that a profile can be triggered by a command that isn't taking up space in the drop down in the app. One example is so that the default profile can start in some useful directory "C:\src" while an otherwise identical profile can start in ".". This is useful because then a profile can start in the current directory without taking up space in the menus. I am using this so I can right click and have "Open windows terminal here" in the context menu. Obviously the profile for "Open windows terminal here" is not needed in the menus. # Actual behavior The hidden profile is not targetable and the default profile is chosen.
claunia added the Resolution-Duplicate label 2026-01-31 02:50:58 +00:00
claunia commented 2026-01-31 02:50:59 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 23, 2020):

You're in luck! This was fixed in 1.5 (currently in preview) and is a /duplicate of #4139

@DHowett commented on GitHub (Nov 23, 2020): You're in luck! This was fixed in 1.5 (currently in preview) and is a /duplicate of #4139
claunia commented 2026-01-31 02:50:59 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 23, 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 (Nov 23, 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!
claunia commented 2026-01-31 02:50:59 +00:00
Author
Owner
Copy Link

@jmahlers commented on GitHub (Nov 23, 2020):

Awesome, sorry I didnt find that before. Thanks!

@jmahlers commented on GitHub (Nov 23, 2020): Awesome, sorry I didnt find that before. Thanks!
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#11552
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?