-
Notifications
You must be signed in to change notification settings - Fork 55
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
Windows support #80
Comments
Is this still an issue? I don't have a Windows machine to test. 1 & 2 don't seem relevant to our code. We don't do terminal detection and unconditionally emit ANSI control sequences today. 3 is not a goal. Use the If 4 is still an issue, you can send a PR to |
This comment was marked as outdated.
This comment was marked as outdated.
|
I was playing around and I was having problems making it work out of the box, but I did it in the end. I'm opening an issue instead of a PR, because I'm not sure in what style would you apply these changes. The main fix that's absolutely necessary is patch 2 for
jansi
(see 4.).Below is what I observed and learned:
IntelliJ IDEA terminal view supports color and relocation of cursor
(Gradle output is colored and workers are shown)
Gradle
:run
task isJavaExec
type and it messes with System.out in some waySee Document how to enable color-coded output from bootRun spring-projects/spring-boot#24169 where they gave up supporting colors in Gradle, this seems to be because of Can't use System.console() with the Gradle Daemon gradle/gradle#1251, but this assumption is not conclusive as they're talking about console input there.
:jar
insamples
doesn't produce a runnable jar file even though theapplication
plugin is applied. (easy fix)Patch 1: make jar runnable
Applied to each sample:
jansi
is not set up correctly in mosaic, because it detects tty, but is not rendering correctlyExample unprocessed ansi output
Patch 2: set up jansi as documented
At this point running
gradlew -p samples :jest:jar
and thenjava -jar samples\jest\build\libs\jest.jar
works nicely (ignoring Unicode problems)The text was updated successfully, but these errors were encountered: