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

Terminal rendering vs. console rendering #1970

Closed
cerebrate opened this issue Jul 14, 2019 · 2 comments
Closed

Terminal rendering vs. console rendering #1970

cerebrate opened this issue Jul 14, 2019 · 2 comments
Labels
Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@cerebrate
Copy link

Environment

Windows build number: 18922
Windows Terminal version (if applicable): 0.2.1831.0

Any other software?

This particular example was generated on Debian Buster with ponysay 3.2.0, but the same rendering issue occurs with other combinations; this is just the one that makes it most obvious.

Steps to reproduce

With WSL installed and a WSL prompt open in Windows Terminal:

sudo apt install ponysay
ponysay -q

Expected behavior

renderingdifferences

ASCII art image on the left (Terminal) should match ASCII art image on the right (console), without blur, jaggies, or superfluous underlines.

Actual behavior

It, well, doesn't.
@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 Jul 14, 2019
@DHowett-MSFT
Copy link
Contributor

This is probably some combination of #1703, #1626, #404, and #455!

@DHowett-MSFT DHowett-MSFT added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jul 14, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 14, 2019
@cerebrate
Copy link
Author

Aaah, I missed #455

I've subscribed to all those; will re-open if this persists once they're resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cerebrate @DHowett-MSFT