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

Exposing LVB Grid through VT #10932

Closed
alabuzhev opened this issue Aug 12, 2021 · 2 comments
Closed

Exposing LVB Grid through VT #10932

alabuzhev opened this issue Aug 12, 2021 · 2 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

@alabuzhev
Copy link
Contributor

Description of the new feature/enhancement

When ENABLE_LVB_GRID_WORLDWIDE mode is set, it's possible to use COMMON_LVB_* flags to emphasize portions of output.
It's a neat feature (thank you), but it only works with WriteConsoleOutput API, which is now considered legacy and doesn't support extended colours and attributes.

It would be nice to have the grid attributes accessible through ESC sequences.

@alabuzhev alabuzhev added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 12, 2021
@ghost ghost 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 Aug 12, 2021
@DHowett
Copy link
Member

DHowett commented Aug 12, 2021

Funny enough, we're tracking this one in /dup #8037!

@ghost
Copy link

ghost commented Aug 12, 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 ghost closed this as completed Aug 12, 2021
@ghost ghost 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 Aug 12, 2021
This issue was closed.
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

2 participants