Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Colorful output with user defined tyext pattern #16604

Closed
SigmaStar opened this issue Jan 26, 2024 · 4 comments
Closed

Colorful output with user defined tyext pattern #16604

SigmaStar opened this issue Jan 26, 2024 · 4 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@SigmaStar
Copy link

Description of the new feature/enhancement

I hope terminal can equipped with function that can colorized some text which user defined in settings.json.
For example in settings.json user can write some PCRE2 pattern like "ERROR \b\w+\b" and set the text color to red. Then as soon as ERROR something appeared on terminal, the terminal output the text in red color.

Proposed technical implementation details (optional)

maybe add some hooks on output? But will this cause performance impact for user?
@SigmaStar SigmaStar added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jan 26, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jan 26, 2024
@SigmaStar
Copy link
Author

Maybe we can reuse the function " auto detect url"?

@lhecker
Copy link
Member

lhecker commented Jan 26, 2024

We're tracking something like this over at #5916. Please let me know if your idea is different from what's described there. Otherwise, I believe we can close this issue as a duplicate. 🙂

@lhecker lhecker added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jan 26, 2024
@SigmaStar
Copy link
Author

oh, yes! this is a duplicated issue.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jan 27, 2024
@SigmaStar
Copy link
Author

I've closed

@SigmaStar SigmaStar closed this as not planned Won't fix, can't repro, duplicate, stale Jan 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lhecker @SigmaStar