starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Questions] Hidden Profiles and Current Session Control? #8169

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

Originally created by @mascalia on GitHub (May 15, 2020).

Sorry for being a noob (to WT, not to Powershell), but can someone help me out with a few questions?

  1. How, exactly, do you access hidden profiles in WT command-line? They don't show up in the drop-down (naturally, which is what I want), but I'd like to be able to spawn them when starting WT with a command-line argument (-p and --profile don't work, they only cause the default profile to come up).

  2. If you start terminal with Powershell, is there any way to control the WT session from within the session? For example, if I start with a bog-standard Powershell profile, is there any way within that session to split the pane and start a new powershell script?

The goal with Q2 is to avoid having to write a set of chained command-line WT arguments, and instead simply start a profile and then run a .ps1 script that will configure the running profile however I want.

Thanks in advance for any help.

Originally created by @mascalia on GitHub (May 15, 2020). Sorry for being a noob (to WT, not to Powershell), but can someone help me out with a few questions? 1. How, exactly, do you access hidden profiles in WT command-line? They don't show up in the drop-down (naturally, which is what I want), but I'd like to be able to spawn them when starting WT with a command-line argument (-p and --profile don't work, they only cause the default profile to come up). 2. If you start terminal with Powershell, is there any way to control the WT session from within the session? For example, if I start with a bog-standard Powershell profile, is there any way within that session to split the pane and start a new powershell script? The goal with Q2 is to avoid having to write a set of chained command-line WT arguments, and instead simply start a profile and then run a .ps1 script that will configure the running profile however I want. Thanks in advance for any help.
claunia added the Resolution-Duplicate label 2026-01-31 01:22:29 +00:00
claunia commented 2026-01-31 01:22:29 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 15, 2020):

Hey, thanks for asking! These aren't "noob" questions by any means. These are the ones with somewhat complicated answers 😄

  1. Right now, {profile}.hidden is a bit of a misnomer. Hidden profiles are actually, uh, deleted. They're ex-profiles. They've joined the choir invisible. We have #4139 tracking fixing that.
  2. WT doesn't support any sort of "remote control" mechanism right now, but we're tracking that in #4472. We're putting together our thoughts on a multiprocess model and how we'll handle IPC to make sure we're making the right call here.

Right now, the go-to solution for having Terminal start up the way you want is to make a shortcut to wt.exe with the args you want. It's not ideal, but it may suffice for now. 😄

/dup #4139 #4472.

@DHowett-MSFT commented on GitHub (May 15, 2020): Hey, thanks for asking! These aren't "noob" questions by any means. These are the ones with somewhat complicated answers :smile: 1. Right now, `{profile}.hidden` is a bit of a misnomer. Hidden profiles are actually, uh, deleted. They're ex-profiles. They've joined the choir invisible. We have #4139 tracking fixing that. 2. WT doesn't support any sort of "remote control" mechanism right now, but we're tracking that in #4472. We're putting together our thoughts on a multiprocess model and how we'll handle IPC to make sure we're making the right call here. Right now, the go-to solution for having Terminal start up the way you want is to make a shortcut to `wt.exe` with the args you want. It's not ideal, but it may suffice for now. :smile: /dup #4139 #4472.
claunia commented 2026-01-31 01:22:30 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 15, 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 (May 15, 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!
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#8169
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?