JANSI does not work within an IntelliJ IDEA console (Application run configuration) #31
Comments
|
+1 |
rnorth
added a commit
to rnorth/visible-assertions
that referenced
this issue
Jan 8, 2016
…TTY support. As a result of this, no run output will be coloured in IntelliJ, but this seems marginally better than having output that is corrupt when viewed in certain modes. This is a workaround for issues described elsewhere: fusesource/jansi#31 https://youtrack.jetbrains.com/issue/IDEA-132822 Refs #1
|
+1 |
rnorth
added a commit
to rnorth/visible-assertions
that referenced
this issue
Jul 15, 2017
…TTY support. As a result of this, no run output will be coloured in IntelliJ, but this seems marginally better than having output that is corrupt when viewed in certain modes. This is a workaround for issues described elsewhere: fusesource/jansi#31 https://youtrack.jetbrains.com/issue/IDEA-132822 Refs #1
rnorth
added a commit
to rnorth/visible-assertions
that referenced
this issue
Jul 15, 2017
…TTY support. As a result of this, no run output will be coloured in IntelliJ, but this seems marginally better than having output that is corrupt when viewed in certain modes. This is a workaround for issues described elsewhere: fusesource/jansi#31 https://youtrack.jetbrains.com/issue/IDEA-132822 Refs #1
|
+1 |
1 similar comment
|
+1 |
|
As a workaround, my IntelliJ run configuration uses VM options "-Djansi.passthrough=true" |
Oh,it's working perfectly. |
|
not sure if there is a global switch |
|
+1 |
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The jansi detection does not work correctly when running an application within an IntelliJ IDEA console, because stdout and stderr are redirected. Jansi could detect this situation and pass through the ANSI stream without any changes for proper operation within IntelliJ. See:
https://youtrack.jetbrains.com/issue/IDEA-132822
The text was updated successfully, but these errors were encountered: