Explicitly configure TERM env var to skirt around Git progress issue on Windows #9003
Conversation
This file contains 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
On Windows we apparently have to explicitly set it to 'dumb' for the is_terminal_dumb check to return true. See #8962
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
On Windows we apparently have to explicitly set
TERMtodumbfor theis_terminal_dumbcheck to return true. See #8962Description
On Windows we have to explicitly set it to 'dumb' for the is_terminal_dumb check to return true. See #8962 for the background
Screenshots
Release notes
Notes: [Fixed] Inaccurate Git Progress parsing on Window