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

Highlight terminal output based on regex pattern #13644

New Issue
Closed
opened 2026-01-31 03:48:12 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 03:48:12 +00:00
Owner
Copy Link

Originally created by @mikhail-naumenko on GitHub (Apr 27, 2021).

Description of the new feature/enhancement

That would be really handy to have an ability to apply some custom highlighting to terminal output.
For example when I read logs generated by some application I want to highlight particular feature name I'm interested in. So if logs of this feature start with Info: [Feature name] log message, I want to highlight "[Feature name]" with yellow.

That should be an ability to specify various highlighting rules. E.g. I have the following outputs
error: [feature 1] error message here
warning: [feature 2] some another message
info: [feature 3] yet another message

In this case I want to highlight "error:" with red, "warning:" with yellow, "info with green and "debug" with blue. And of course that would be cool if I highlight different features with different colors.

Just to emphasize. That is not mandatory that patterns are at the beginning of the string. It could be in any part of the string.

Proposed technical implementation details

A set of rules in settings.json which associate regex pattern with color. E.g.:

{
    "highlightRules": [
        "pattern": "^error:",
        "color": "red"
    ], [
        "pattern": "\[feature name\]",
        "color": "#deab1f"
    ], [
        "pattern" "^(?:\d{2,4}-?)+\s(?:\d{2,3}[:\.]?)+", // date pattern
        "color": "#34ebe1"
    ]
}
Originally created by @mikhail-naumenko on GitHub (Apr 27, 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 That would be really handy to have an ability to apply some custom highlighting to terminal output. For example when I read logs generated by some application I want to highlight particular feature name I'm interested in. So if logs of this feature start with Info: [Feature name] log message, I want to highlight "[Feature name]" with yellow. That should be an ability to specify various highlighting rules. E.g. I have the following outputs error: [feature 1] error message here warning: [feature 2] some another message info: [feature 3] yet another message In this case I want to highlight "error:" with red, "warning:" with yellow, "info with green and "debug" with blue. And of course that would be cool if I highlight different features with different colors. Just to emphasize. That is not mandatory that patterns are at the beginning of the string. It could be in any part of the string. <!-- 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). --> # Proposed technical implementation `details` A set of rules in `settings.json` which associate regex pattern with color. E.g.: ``` { "highlightRules": [ "pattern": "^error:", "color": "red" ], [ "pattern": "\[feature name\]", "color": "#deab1f" ], [ "pattern" "^(?:\d{2,4}-?)+\s(?:\d{2,3}[:\.]?)+", // date pattern "color": "#34ebe1" ] } ``` <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 03:48:12 +00:00
claunia commented 2026-01-31 03:48:13 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Apr 27, 2021):

Similar request: #7561

@skyline75489 commented on GitHub (Apr 27, 2021): Similar request: #7561
claunia commented 2026-01-31 03:48:14 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Apr 27, 2021):

#7561 and #3920 both focus on highlighting search result. Do people really want to highlight output (of certain pattern) all the time ? I don't know. I feel colored output is good enough for me personally.

@skyline75489 commented on GitHub (Apr 27, 2021): #7561 and #3920 both focus on highlighting *search* result. Do people really want to highlight output (of certain pattern) *all the time* ? I don't know. I feel colored output is good enough for me personally.
claunia commented 2026-01-31 03:48:14 +00:00
Author
Owner
Copy Link

@mikhail-naumenko commented on GitHub (Apr 27, 2021):

#7561 and #3920 both focus on highlighting search result. Do people really want to highlight output (of certain pattern) all the time ? I don't know. I feel colored output is good enough for me personally.

Yes that would be good to highlight output on regular basis and the difference of this request from #7561 is that you wouldn't have any dialog open when output is highlighted.

That would be also cool if that could look more like code highlighting then search results highlighting.

@mikhail-naumenko commented on GitHub (Apr 27, 2021): > > > #7561 and #3920 both focus on highlighting _search_ result. Do people really want to highlight output (of certain pattern) _all the time_ ? I don't know. I feel colored output is good enough for me personally. Yes that would be good to highlight output on regular basis and the difference of this request from #7561 is that you wouldn't have any dialog open when output is highlighted. That would be also cool if that could look more like code highlighting then search results highlighting.
claunia commented 2026-01-31 03:48:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 29, 2021):

Yea, generally we're tracking this in #3920 and linked threads. I know #8294 mentions "links", but I think a lot of what that's tracking would apply to even not links.

/dup #7561
/dup #3920
/dup #8294

@zadjii-msft commented on GitHub (Apr 29, 2021): Yea, generally we're tracking this in #3920 and linked threads. I know #8294 mentions "links", but I think a lot of what that's tracking would apply to even not links. /dup #7561 /dup #3920 /dup #8294
claunia commented 2026-01-31 03:48:14 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 29, 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 (Apr 29, 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!
claunia commented 2026-01-31 03:48:14 +00:00
Author
Owner
Copy Link

@jonny64 commented on GitHub (Sep 16, 2025):

impact: find errors faster

this is not the same as highlight find results, just try it

@jonny64 commented on GitHub (Sep 16, 2025): * mobaxterm has this feature https://stackoverflow.com/questions/64391031/how-to-use-customize-syntax-highlighting-on-mobaxterm * it has by default pretty good defaults: highlight err* warn* etc impact: find errors faster this is not the same as highlight find results, just try it
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#13644
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?