starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Add ability to run in background #14224

New Issue
Closed
opened 2026-01-31 04:04:19 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 04:04:19 +00:00
Owner
Copy Link

Originally created by @Gravifer on GitHub (Jun 13, 2021).

Description of the new feature/enhancement

I think it would be more convenient to be able to put the terminal host in the background.

As I imagine, in the fullest form:

  • when any instance is put to the background (which may be set as the default behavior when the window is minimized), the host leaves an icon in the task bar;
  • when the icon is clicked, a menu pops up and lists all running instances, with simple notification (running/error/finished) of status for each.
Originally created by @Gravifer on GitHub (Jun 13, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> I think it would be more convenient to be able to put the terminal host in the background. As I imagine, in the fullest form: - when any instance is put to the background (which may be set as the default behavior when the window is minimized), the host leaves an icon in the task bar; - when the icon is clicked, a menu pops up and lists all running instances, with simple notification (running/error/finished) of status for each. <!-- # Proposed technical implementation details (optional) --> <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 04:04:19 +00:00
claunia commented 2026-01-31 04:04:21 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jun 14, 2021):

This is related to the defterm stuff. You can execute a long running script on conhost and the console window can be hidden and run in the background. With Windows Terminal able to become the default console, it should provide similar functionality/experience. The Terminal devs are still fleshing out issues with the defterm and I think you require an Insiders build to test it out.

@WSLUser commented on GitHub (Jun 14, 2021): This is related to the defterm stuff. You can execute a long running script on conhost and the console window can be hidden and run in the background. With Windows Terminal able to become the default console, it should provide similar functionality/experience. The Terminal devs are still fleshing out issues with the defterm and I think you require an Insiders build to test it out.
claunia commented 2026-01-31 04:04:21 +00:00
Author
Owner
Copy Link

@Gravifer commented on GitHub (Jun 15, 2021):

@WSLUser thanks for your reply. Maybe I have mistake your argument, but I don't think what I'm suggesting requires Terminal to be the defterm.
I am not clear about the limitations of Terminal's current status, though Chrome and Slack are able to "hide themselves to the task bar", which doesn't seem to require more than standard API (I'm not sure though).
Maybe it is possible to provide a similar experience in Terminal? In this case, neither the shell sessions nor the processes running in them are really put to the background; technically only the Terminal window is hidden.
To my mind, this is enough to provide a decent user experience. This is like using tmux without setting it up as the default shell: it only serves to hold the sessions and prevents accidental hang up.

@Gravifer commented on GitHub (Jun 15, 2021): @WSLUser thanks for your reply. Maybe I have mistake your argument, but I don't think what I'm suggesting requires Terminal to be the defterm. I am not clear about the limitations of Terminal's current status, though Chrome and Slack are able to "hide themselves to the task bar", which doesn't seem to require more than standard API (I'm not sure though). Maybe it is possible to provide a similar experience in Terminal? In this case, neither the shell sessions nor the processes running in them are really put to the background; technically only the Terminal window is hidden. To my mind, this is enough to provide a decent user experience. This is like using tmux without setting it up as the default shell: it only serves to hold the sessions and prevents accidental hang up.
claunia commented 2026-01-31 04:04:21 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Jun 15, 2021):

I think this is similar to #5727?

@skyline75489 commented on GitHub (Jun 15, 2021): I think this is similar to #5727?
claunia commented 2026-01-31 04:04:21 +00:00
Author
Owner
Copy Link

@Gravifer commented on GitHub (Jun 15, 2021):

@skyline75489 you're right. Sorry for overlooking similar issues in my initial search.

@Gravifer commented on GitHub (Jun 15, 2021): @skyline75489 you're right. Sorry for overlooking similar issues in my initial search.
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-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#14224
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?