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

Indicate tabs that received any output in it console #13177

New Issue
Closed
opened 2026-01-31 03:35:39 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 03:35:39 +00:00
Owner
Copy Link

Originally created by @iuricarraro on GitHub (Mar 25, 2021).

Description of the new feature/enhancement

When you have many tabs it is would be interesting to signal when a tab is outputting data and which tab doing this.

The idea is show a little bubble in the right corner of the tab to indicate this.

In many job we uses many tabs to watch logs in real time.

Get-Content -Path .\test.log -Wait | Select-String -Pattern 'ERROR'

It is used for many different parallel environments, and this signal will be usefully to monitor efficiently this tabs.

Proposed technical implementation details (optional)

When a tab, without focus, receives some output data, a ball/bubble of some color should appear indicating that there has been an update on that console.
Just like second image.

1
2

Originally created by @iuricarraro on GitHub (Mar 25, 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 When you have many tabs it is would be interesting to signal when a tab is outputting data and which tab doing this. The idea is show a little bubble in the right corner of the tab to indicate this. <!-- 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). --> In many job we uses many tabs to watch logs in real time. ``` Get-Content -Path .\test.log -Wait | Select-String -Pattern 'ERROR' ``` It is used for many different parallel environments, and this signal will be usefully to monitor efficiently this tabs. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> When a tab, without focus, receives some output data, a ball/bubble of some color should appear indicating that there has been an update on that console. Just like second image. ![1](https://user-images.githubusercontent.com/4460055/112417735-f2eef980-8d06-11eb-9118-118ae1fdd478.png) ![2](https://user-images.githubusercontent.com/4460055/112417736-f3879000-8d06-11eb-982a-136fa9a46e3d.png)
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 03:35:39 +00:00
claunia commented 2026-01-31 03:35:40 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 25, 2021):

I think #7955 covers this?

@skyline75489 commented on GitHub (Mar 25, 2021): I think #7955 covers this?
claunia commented 2026-01-31 03:35:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 25, 2021):

Yep, sure does!

/dup #7955

@zadjii-msft commented on GitHub (Mar 25, 2021): Yep, sure does! /dup #7955
claunia commented 2026-01-31 03:35:40 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 25, 2021):

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 (Mar 25, 2021): 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 Issue-Feature 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#13177
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?