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

Tab in-/activity monitoring #19560

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

Originally created by @iconoeugen on GitHub (Mar 20, 2023).

Description of the new feature/enhancement

The Terminal application supports multiple tabs which makes difficult to track when a change happens in other tabs then the current one that is in focus.

The new feature should introduce the possibility to configure in-/activity monitoring for each tab individually, that would enable the user to skip switching between different tabs in order to observe if any change took place outside of the current tab that is in focus.

Proposed technical implementation details (optional)

Add support to configure monitor for:

  • Silence: Toggles the monitoring of the current tab for lack of activity
    By default, after 10 seconds of inactivity, an info icon will appear on the session’s tab.
  • Activity: Toggles the monitoring of the current tab for activity
    Upon any activity, an info icon will appear on the session’s tab.
  • Process Finishing: Toggles the monitoring of the current tab for the process finishing.
    If checked, upon finishing the current process, Terminal will show a notification The process ’name of the process’ has finished running in session ’name of the session’.

Optional the alarming of in-/activity can be accompanied by an acoustic bell that should be mutable by preference

Originally created by @iconoeugen on GitHub (Mar 20, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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). --> The Terminal application supports multiple tabs which makes difficult to track when a change happens in other tabs then the current one that is in focus. The new feature should introduce the possibility to configure in-/activity monitoring for each tab individually, that would enable the user to skip switching between different tabs in order to observe if any change took place outside of the current tab that is in focus. # Proposed technical implementation details (optional) Add support to configure monitor for: - **Silence**: Toggles the monitoring of the current tab for lack of activity By default, after 10 seconds of inactivity, an info icon will appear on the session’s tab. - **Activity**: Toggles the monitoring of the current tab for activity Upon any activity, an info icon will appear on the session’s tab. - **Process Finishing**: Toggles the monitoring of the current tab for the process finishing. If checked, upon finishing the current process, Terminal will show a notification The process ’name of the process’ has finished running in session ’name of the session’. *Optional* the alarming of in-/activity can be accompanied by an acoustic bell that should be mutable by preference
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixNeeds-Author-Feedback labels 2026-01-31 06:47:16 +00:00
claunia commented 2026-01-31 06:47:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 20, 2023):

Hmm, there's a lot of overlap between #1620, and more specifically #7955.

  • silence: you know, I don't think there's anything we have tracking "this tab hasn't done anything in a while", though, to me, that sounds like the inverse of "display an icon when the tab has done something", so maybe that would be good enough?
  • activity: Yea that's the thing tracked in those threads
  • Process Finishing: This is... harder. And might require more refinement of the request. Do you want to know when just the root process launched by the Terminal died? Any child of that process? (that wouldn't really work for WSL and certainly not as expected for SSH). What kind of notification are you looking for? An OS-level notification, ala #14425? An in-app toast?

How does https://github.com/microsoft/terminal/issues/7955#issuecomment-1303740796 sound/?

@zadjii-msft commented on GitHub (Mar 20, 2023): Hmm, there's a lot of overlap between #1620, and more specifically #7955. * **silence**: you know, I don't think there's anything we have tracking "this tab _hasn't_ done anything in a while", though, to me, that sounds like the inverse of "display an icon when the tab _has_ done something", so maybe that would be good enough? * **activity**: Yea that's the thing tracked in those threads * **Process Finishing**: This is... harder. And might require more refinement of the request. Do you want to know when just the root process launched by the Terminal died? Any child of that process? (that wouldn't really work for WSL and certainly not as expected for SSH). What kind of notification are you looking for? An OS-level notification, ala #14425? An in-app toast? How does https://github.com/microsoft/terminal/issues/7955#issuecomment-1303740796 sound/?
claunia commented 2026-01-31 06:47:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2023):

Hey all, our bot's been acting up the last few weeks. This issue has been marked as requiring author feedback, but hasn't had any activity in the last week. We're gonna close it to tidy up. Feel free to continue the discssion in the comments - we can always reopen if new information comes to light. Thanks!

@zadjii-msft commented on GitHub (Apr 13, 2023): Hey all, our bot's been acting up the last few weeks. This issue has been marked as requiring author feedback, but hasn't had any activity in the last week. We're gonna close it to tidy up. Feel free to continue the discssion in the comments - we can always reopen if new information comes to light. 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-Author-Feedback 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#19560
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?