hidden profiles are deleted, not hidden #5816

Closed
opened 2026-01-31 00:22:32 +00:00 by claunia · 3 comments
Owner

Originally created by @DHowett-MSFT on GitHub (Jan 7, 2020).

Originally assigned to: @DHowett on GitHub.

Right now, "hiding" a profile totally deletes it. This has some interesting effects on profiles that are in active use - their icons and background images disappear, and their closeOnExits get ignored. Anything that relies on the presence of a profile for a given tab fails.

I'm wondering if hidden shouldn't just mean "don't show in the list". This has other interesting follow-on questions: should a profile that's been hidden still be launchable with a keyboard shortcut that specifically targets it? should a hidden profile be defaultable? I don't totally see why not.

Partially related to [workitem for customizing the dropdown menu].

Originally created by @DHowett-MSFT on GitHub (Jan 7, 2020). Originally assigned to: @DHowett on GitHub. Right now, "hiding" a profile totally deletes it. This has some interesting effects on profiles that are in active use - their icons and background images disappear, and their `closeOnExit`s get ignored. Anything that relies on the _presence_ of a profile for a given tab fails. I'm wondering if `hidden` shouldn't just mean "don't show in the list". This has _other_ interesting follow-on questions: should a profile that's been hidden still be launchable with a keyboard shortcut that specifically targets it? should a hidden profile be defaultable? I don't totally see why not. Partially related to [workitem for customizing the dropdown menu].
claunia added the Resolution-Fix-CommittedArea-SettingsIssue-TaskProduct-Terminal labels 2026-01-31 00:22:32 +00:00
Author
Owner

@acshef commented on GitHub (Feb 18, 2020):

A hidden profile also can't be started using the command line argument wt -p introduced in v0.9. I believe that behavior to be a bug. The generally observed behavior of "hidden things" in UX/UI is that they can still be accessed explicitly -- I view that as one of the principal distinctions between hidden and deleted things.

@acshef commented on GitHub (Feb 18, 2020): A hidden profile also can't be started using the command line argument `wt -p` introduced in v0.9. I believe that behavior to be a bug. The generally observed behavior of "hidden things" in UX/UI is that they can still be accessed explicitly -- I view that as one of the principal distinctions between hidden and deleted things.
Author
Owner

@zadjii-msft commented on GitHub (Jul 30, 2020):

@WSLUser For the record, this mostly just means that the profile is deleted from our runtime list of profiles, which means that you cannot reference it in any actions or commandline args, not that it's "uninstalled". The code that makes the Azure shell work is built-in to the Terminal - it's basically just a thin wrapper for a web API to establish the connection.

@zadjii-msft commented on GitHub (Jul 30, 2020): @WSLUser For the record, this mostly just means that the profile is deleted from our runtime list of profiles, which means that you cannot reference it in any actions or commandline args, not that it's "uninstalled". The code that makes the Azure shell work is built-in to the Terminal - it's basically just a thin wrapper for a web API to establish the connection.
Author
Owner

@ghost commented on GitHub (Nov 11, 2020):

:tada:This issue was addressed in #8070, which has now been successfully released as Windows Terminal Preview v1.5.3142.0.🎉

Handy links:

@ghost commented on GitHub (Nov 11, 2020): :tada:This issue was addressed in #8070, which has now been successfully released as `Windows Terminal Preview v1.5.3142.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.5.3142.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5816