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

Capability to set a alternative default profile when launchen the terminal over the windows explorer context menu #18510

New Issue
Closed
opened 2026-01-31 06:16:15 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 06:16:15 +00:00
Owner
Copy Link

Originally created by @dfoxg on GitHub (Sep 20, 2022).

Description of the new feature/enhancement

At the moment we can specify the default profile when the windows terminal is getting started. Under Windows 11 I miss the option, to specify which profile should be getting used when i start the terminal over the windows explorer context menu.

At least in my setup i´m normaly using WSL so thats my standard profile. But when I´m starting the terminal over the context menu, i want to use cmd. Of course i can manually open the cmd but then i´m losing the directory context and have to manually cd into the right path.

I would love to see an option where i can specifiy, which profile should be used when the terminal is getting started over the explorer context menu.

Proposed technical implementation details (optional)

Maybe a second dropdown in the settings?

Originally created by @dfoxg on GitHub (Sep 20, 2022). # Description of the new feature/enhancement At the moment we can specify the default profile when the windows terminal is getting started. Under Windows 11 I miss the option, to specify which profile should be getting used when i start the terminal over the windows explorer context menu. At least in my setup i´m normaly using `WSL` so thats my standard profile. But when I´m starting the terminal over the context menu, i want to use `cmd`. Of course i can manually open the `cmd` but then i´m losing the directory context and have to manually `cd` into the right path. I would love to see an option where i can specifiy, which profile should be used when the terminal is getting started over the explorer context menu. # Proposed technical implementation details (optional) Maybe a second dropdown in the settings?
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 06:16:16 +00:00
claunia commented 2026-01-31 06:16:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 20, 2022):

Alternatively, would #6111 work for you/? Instead of specifying a different default profile for the context menu, just changing the menu to allow you to pick whichever profile you want?

@zadjii-msft commented on GitHub (Sep 20, 2022): Alternatively, would #6111 work for you/? Instead of specifying a different default profile for the context menu, just changing the menu to allow you to pick whichever profile you want?
claunia commented 2026-01-31 06:16:17 +00:00
Author
Owner
Copy Link

@dfoxg commented on GitHub (Sep 20, 2022):

@zadjii-msft yes, that would be working too. Looks like a more straight forward solution! I will close this issue in preference for #6111.

Thanks!

@dfoxg commented on GitHub (Sep 20, 2022): @zadjii-msft yes, that would be working too. Looks like a more straight forward solution! I will close this issue in preference for #6111. 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 Issue-Feature Needs-Attention 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#18510
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?