Skip to content

TSCBasic: enable proper rendering on Windows #294

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

Merged
merged 1 commit into from
Mar 4, 2022

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Mar 4, 2022

This restores the behaviour of rendering on Windows after a very long
time. However, since TERM is not an environment variable on Windows,
simply elide the check for that. This finally gives us proper rendering
on Windows.

This restores the behaviour of rendering on Windows after a very long
time.  However, since `TERM` is not an environment variable on Windows,
simply elide the check for that.  This finally gives us proper rendering
on Windows.
@compnerd
Copy link
Member Author

compnerd commented Mar 4, 2022

This depends on swiftlang/swift-package-manager#4192 to get proper rendering.

@compnerd
Copy link
Member Author

compnerd commented Mar 4, 2022

@swift-ci please test

Copy link
Contributor

@tomerd tomerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a test we can add?

@compnerd
Copy link
Member Author

compnerd commented Mar 4, 2022

I think that is part of the problem, I don't have a good way to test this in a test case. The behaviour is not something that is entirely in our control. It requires synchronization between a test application, OS, llbuild, and s-p-m. On this own this is just undoing the blanket "do not support rendering terminals". This was a workaround for the underlying problem which has now been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants