Hyper: Gradle build output is messed up

[NomNuggetNom]

• [x] I am on the latest Hyper.app version
• [x] I have searched the issues of this repo and believe that this is not a duplicate

• OS version and name: Windows 10 x64 Build 15063
• Hyper.app version: 2.0.4 (canary)
• Link of a Gist with the contents of your .hyper.js: https://gist.github.com/NomNuggetNom/b71dcd3984117c1a949315339b48f03b
• Relevant information from devtools _(CMD+ALT+I on Mac OS, CTRL+SHIFT+I elsewhere)_: N/A
• The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue

When issuing a build with gradle, it seems to try and detect what colors to show. Whatever it decides upon, the terminal can't handle it properly. Here's a sample screenshot:

As you can see, other colors work in the console, but whatever Gradle is trying to do, it doesn't work. I'm not sure if this is a Gradle issue, but this DOES NOT happen in the native terminal that comes with git bash. Comparison:

[NomNuggetNom]

@albinekb Any more info I can provide for this?

[albinekb]

Don't think so, I can take a look soon if I can reproduce 👍

[NomNuggetNom]

@albinekb Any luck? Happy to try and help if I can!

[NomNuggetNom]

I fixed this myself after some annoying debugging. Hyper sets the TERM environment to xterm-256 (I think this is Hyper's doing), which changes the way Gradle does the output. To fix this, I set it manually in my config:

env: {
   TERM: 'cygwin'
}

I'm not sure who's end this problem originates on. Feel free to close if you think it's a Gradle issue.

[stevenjlho]

@NomNuggetNom It works, thank you.

[ghost]

@albinekb Is there a plan for a long-term solution? Changing the config file just to fix hyper for gradle doesn't seem like a good long term solution to me.

[kevinwtenweerde]

I still experience this issue when running a gradlew bootRun command.
V2.1.0-canary.2. Tried to set the env to cygwin. No difference for me.