This ticket originates in research done for epinio/epinio/issues/673, itself a follow up of epinio/epinio/issues/494
The relevant setup is
- Platform: Win 10 Home (Virtual Machine, Linux-hosted, VirtualBox)
- Modules (
grep 'fatih\|mattn' go.mod):
- github.com/fatih/color v1.12.0
- github.com/mattn/go-isatty v0.0.12
- Sum Modules (
grep 'fatih\|mattn' go.sum |grep -v go.mod):
- github.com/fatih/color v1.12.0 h1:mRhaKNwANqRgUBGKmnI5ZxEk7QXmjQeCcuYFMX2bfcc=
- github.com/mattn/go-colorable v0.1.8 h1:c1ghPdyEDarC70ftn0y+A/Ee++9zz8ljHG1b13eJ0s8=
- github.com/mattn/go-isatty v0.0.12 h1:wuysRhFDzyxgEmMf5xjvJ2M9dZoWAXNNr5LSBS7uHXY=
- github.com/mattn/go-runewidth v0.0.7 h1:Ei8KR0497xHyKJPAv59M1dkC+rOZCMBJ+t3fZ+twI54=
go.mod lines I see a lot more versions for all the packages.
Below a screenshot demonstrating the differences between a mingw bash (from git for windows) on one side, and cmd.exe and PowerShell on the other side:
While I originally thought that maybe the
IsTerminal generates an incorrect result, disabling handling with the output from my last tests I now have to suspect an issue either here in
go-colorable, or in its user, https://github.com/fatih/color, which is the actual package used by the epinio code. And I do not see how our use of the
fatih/color would be incorrect.
With regard to the version numbers,
fatih/color is at 1.12.0, the latest release as of May 24 this year.
Which in turn uses the latest tag 0.1.8 for
go-colorable, as of Oct 3 last year.
Any ideas where else to look for the issue ?