running targets without exiting leaves the console screen buffer output mode changed #482
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
adamralph
force-pushed
the
reset-console
branch
from
a5146f5
to
9a8892e
Compare
adamralph
changed the title
adamralph
force-pushed
the
reset-console
branch
from
9a8892e
to
718dcaf
Compare
adamralph
force-pushed
the
reset-console
branch
from
718dcaf
to
0e70049
Compare
|
Released in 3.6.0-rc.1. |
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.
Version(s)
1.2.0to3.5.0.To reproduce
Steps to reproduce the behavior:
RunTargetsWithoutExitingwithout the--no-coloroption.Expected behavior
The console screen buffer output mode is the same as before calling the method.
Actual behaviour
The console screen buffer output mode is 7.
Workarounds
Record the original console screen buffer output mode before calling the method and reset it after calling the method.