After updating to Windows 10 anniversary update(1607), the artisan text in Windows CMD becomes garbled.
Is there any way to fix this?
I've tried the legacy console option but not working.
Asked
Active
Viewed 236 times
0
-
1read some answers here - http://stackoverflow.com/questions/5921556/in-git-bash-on-windows-7-colors-display-as-code-when-running-cucumber-or-rspec. I have got my fixed with unsetting TERM environment variable on git bash when having the same trouble – naneri Aug 12 '16 at 05:35
-
@naneri I'm sorry, after reading I still don't understand. I'm not using Git Bash but Windows CMD. – user77177928 Aug 12 '16 at 06:13
-
Hi, instead of downvoting, can you please explain any fix or workaround? – user77177928 Aug 15 '16 at 09:20
3 Answers
0
Seems like the anniversary update disabled the ansi color.
Let's just wait for the fix.
For now there's a workaround using --no-ansi flag when calling the command.
user77177928
- 465
- 6
- 15
0
Interestingly, if you pipe the colorized output of the command to a output.txt file and then use type output.txt it shows the colors.
It seems like the problem arises from the way cmd is treating output ESC character from programs after the Anniversary Update. (Although, they have added this feature in Insiders Build)
Workaround use Cmder, it's a good alternative to CMD and it still shows colors and of course Unicode characters.
psychob
- 63
- 1
- 6
-
Hi, thanks for the reply. But Instead of using 3rd party, Powershell works fine but I still prefer using CMD.. – user77177928 Sep 29 '16 at 03:11
-
0
I had the same problem. My solution was to set the Backwards-Compatibility of the cmd.exe to Windows 7. After that it worked again.
chris
- 1
-
Hi, where did you set that? My cmd.exe does not have Compatibility tab – user77177928 Oct 17 '16 at 09:41
-
This is weird. I can't find it anymore :( But what is more weird: It works now with Legacymode enabled. – chris Oct 17 '16 at 10:25