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.

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

Currently, Windows Terminal only highlights one found result and users need to input Enter key to iterate all the results. However, there is a feature request on GitHub to highlight all results at once, like what Konsole and iTerm do. This feature can be useful in many ways, such as developers would like to monitor keywords like ERROR, FATAL in real-time output #15017

Closed
jiangdongzi opened this issue Mar 19, 2023 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@jiangdongzi
Copy link

Description of the new feature/enhancement

Proposed technical implementation details (optional)

@jiangdongzi jiangdongzi added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 19, 2023
@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 Mar 19, 2023
@j4james
Copy link
Collaborator

j4james commented Mar 19, 2023

Thanks for the suggestion. The feature for highlighting all search results is tracked in issue #7561. Highlighting keywords like ERROR and FATAL should be covered by the pattern matching functionality tracked in #8294. For more information see also #3920 and #9965.

@zadjii-msft
Copy link
Member

Yep, I couldn't have said it better. Thanks!

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

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Mar 20, 2023
@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants