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

ANSI Artwork appears incorrectly in MysticBBS #5729

Closed
miketheitguy opened this issue May 4, 2020 · 3 comments
Closed

ANSI Artwork appears incorrectly in MysticBBS #5729

miketheitguy opened this issue May 4, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@miketheitguy
Copy link

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19619.0 Microsoft Windows NT 10.0.19619.0

Windows Terminal version (if applicable): 0.11.1191.0

Any other software? Compared against ConEMU v19.10.12.0

Steps to reproduce

  1. Install MysticBBS.
  2. From the terminal, run .\mystic.exe -cfg

Expected behavior

The colors to appear correctly with no breaks in the ANSI artwork.

Actual behavior

Colors appear all over the place and are off. I'm not sure if it's mystic attempting to compensate for Windows or Windows Terminal not displaying colors and artwork properly.
mystic_colors
@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 May 4, 2020
@miketheitguy
Copy link
Author

miketheitguy commented May 4, 2020 •
edited
Loading

This is what it appears as under Ubuntu. Notice that it still shows previous screen data at the bottom of the image.

mystic_linux

@DHowett-MSFT
Copy link
Contributor

/dup #455

@ghost
Copy link

ghost commented May 4, 2020

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 May 4, 2020
@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 May 4, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
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
@miketheitguy @DHowett-MSFT