Display Issues on Windows 10 (garbage characters)

[jednano]

On Windows 10, I'm having display issues in the Command Prompt, PowerShell and different issues in Git Bash. Garbage characters are affecting the display, which you can see in the screenshots below.

Related issues

• Colors aren't parsed properly on Windows? #43
• Issues with windows git bash #62
• Example does not work on windows chjj/blessed#238 (comment)

Windows 10 Command Prompt

Windows 10 PowerShell

Git Bash on Windows 10

Steps to reproduce the problem

1. Ensure you do not have a TERM environment variable set. Note: setting TERM=windows-ansi fixes the problem in the Command Prompt as well as PowerShell, but not Git Bash. Also, I don't see this as a long-term solution.

Please provide a gist of relevant files

https://gist.github.com/jedmao/19cd1eef1b830d53a7857e00b5e30f5a

More Details

• What operating system are you on? Windows 10 Pro, Anniversary Update
• What terminal application are you using? Windows Command Prompt, PowerShell, Git Bash
• What version of webpack-dashboard are you using? 0.1.4
• What is the output of running echo $TERM?
  • Command Prompt: process.env.TERM === undefined See also: Example does not work on windows chjj/blessed#238 (comment)
  • PowerShell: process.env.TERM === undefined See also: Example does not work on windows chjj/blessed#238 (comment)
  • Git Bash: xterm

Note: a console.log before these lines in blessed shows the following in Windows Command Prompt:

options.terminal: undefined
options.term: undefined
process.env.TERM: cygwin
process.platform: win32

[jednano]

@danielverejan windows-ansi in Git Bash didn't work for me.

[jednano]

No. I have not.

[signothefish]

I had the same window appearance as W10 Command Prompt and W10 Power Shell in Putty using UTF-8 encoding. After switching it to ISO-8859-1, the dashboard looks correct.

[LINALIN1979]

@signothefish you are the man! I tried your method to change W8.1 Command Prompt's code page to 437 (United States) and it works. For people who want to try, I suggest to set code page in .bat because it won't change the default code page of command prompt. Here is my .bat for reference

@echo off
call chcp 437
call npm run server.js
pause

[neutraali]

Without delving too deep into the code / related tech, some of these issues could potentially be solved if we had the option of getting the output as UTF-8 -encoded instead of ANSI.

[amokrushin]

@signothefish, maybe that solution will be helpful for PuTTY:
W10 PuTTY, remote host Ubuntu 16.04

Window -> Translation -> Remote character set = UTF-8
Window -> Translation -> Handling of line drawing characters = Use unicode line drawing code points

export NCURSES_NO_UTF8_ACS=1

export LC_ALL=en_US.utf8

[amilajack]

What are thoughts on migrating to https://github.com/Yomguithereal/react-blessed?

[jednano]

@amilajack it's already using blessed, but this is a webpack dashboard, not necessarily anything to do with React.

[kenwheeler]

@amilajack I started with react-blessed, but the feature set required dropping down to regular blessed

[alexgorbatchev]

      LC_ALL: en_US.utf8
      NCURSES_NO_UTF8_ACS: 1

gave me the best results in ConEmu on Windows 10 with webpack-dashboard running inside docker container.

[ryan-roemer]

No recent activity after the workarounds above were posted, so closing. Please feel free anyone to open document PRs if useful, or new issues if there's something in webpack-dashboard@^2 that we should fix. Thanks!

[ChuckJonas]

vscode recently started doing this for me... If I run it in terminal (osx) I don't have any issues.