Issue #1097 - ProgressIndicator uses the stdError #1101
Merged
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
|
Yes, the progress bar definitely should be on stderr, not stdout |
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.
Issue #1097 - ProgressIndicator uses the stdError
Overview
This pull request:
One step closer, but this doesn't solve the problem when a progressBar and a log entry in the same line.
2/4 [==============>-------------] 50% 2 secs/4 secs [info] my log entryBut the stdOutput is clean (or cleaner), so it can be used in pipes.
robo foo | otherThis modification removes the leading
0D 0Acharacters from the stdOutput