Fix windows 10 bold sequence#229
Closed
Vap0r1ze wants to merge 3 commits into
Closed
Conversation
Member
|
This has already been fixed in the latest Windows 10 update: microsoft/WSL#2174 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a problem I've had with a good handful of my projects. After some super deep investigation
/s, I discovered Windows 10 doesn't support the standard bold close sequence like everything else.I added a Windows 10 check to set the closing sequence to a full reset, in the same manner the blue is corrected to bright blue.
I console logged these 3 tagged literals in both versions:
[{red Good morning, {bold Vap0r1ze}.}]Please {bold run} {inverse npm i {bold chalk}}__{underline You have {bold 22} credits}__Top is the new version, bottom is the old
This is how the it looks on Windows 7 & 8 (old and new)
