You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dilijev opened this issue
Jun 3, 2017
· 5 comments
Labels
libuvIssues and PRs related to the libuv dependency or the uv binding.ttyIssues and PRs related to the tty subsystem.windowsIssues and PRs related to the Windows platform.
Version: v8.0.0, v7.10.0, v7.9.0 (does not affect Boron v6.10.3)
Platform: Windows 10 x64 Build 10.0.15063
Subsystem: REPL
After the REPL displays some output to the console, it resets the text color to white instead of the previous foreground color.
Easiest to show with a picture comparing Boron (v6.10.3) to affected versions:
The text was updated successfully, but these errors were encountered:
addaleax
added
libuv
Issues and PRs related to the libuv dependency or the uv binding.
tty
Issues and PRs related to the tty subsystem.
windows
Issues and PRs related to the Windows platform.
labels
Jun 3, 2017
Sometime between 6.10.3 and 7.10.0, Node.js upgraded to a libuv version that uses ANSI codes under Windows 10 (instead of emulating them using Windows-specific calls). That's why this issue doesn't affect Windows 7. See libuv/libuv#889.
The problem is that Windows 10 support for ANSI code seems to be incomplete. Here's the string that is printed when REPL outputs null:
'\u001b[1mnull\u001b[22m'
While "22" is listed in Wikipedia as "Normal color or intensity", it's not listed in MSDN.
Pinging @miniksa since you offered help with the libuv PR. Is my observation correct? Is it planned to add support for the '22' escape code in the future? If not, which escape code would you suggest using to revert boldness?
libuvIssues and PRs related to the libuv dependency or the uv binding.ttyIssues and PRs related to the tty subsystem.windowsIssues and PRs related to the Windows platform.
After the REPL displays some output to the console, it resets the text color to white instead of the previous foreground color.
Easiest to show with a picture comparing Boron (v6.10.3) to affected versions:
The text was updated successfully, but these errors were encountered: