Not properly outputting in MINGW #1925
Comments
|
Looks like the issue here is that MINGW doesn't refresh until stdout is flushed explicitly, whereas most terminal emulators will opt to display text as soon as possible. This shouldn't be too hard to fix. |
|
In the meantime, you should be able to work around the issue by providing the environment variable |
|
@JordonPhillips I put in my environment variables Still same issue. Note that my mingw64 was installed via GIT as the Git Bash terminal. |
JordonPhillips
added a commit
to JordonPhillips/aws-cli
that referenced
this issue
Apr 29, 2016
Some terminal emulators (such as mintty) will not write output to the terminal window until stdout is explicitly flushed. When running `aws configure` a user would see nothing but a new line. After pressing 'enter' four times, they would then see the output flushed all in a single line. This makes it very difficult to configure the command. The solution is to call `flush` after every prompt. Since `raw_input` does not have an option to do this, we have to prompt and flush manually. Since we're already accessing stdout directly, it's easier to write to it directly since print adds some formatting that we don't want (namely, a newline at the end of the print). Fixes aws#1925
JordonPhillips
added a commit
to JordonPhillips/aws-cli
that referenced
this issue
May 2, 2016
Some terminal emulators (such as mintty) will not write output to the terminal window until stdout is explicitly flushed. When running `aws configure` a user would see nothing but a new line. After pressing 'enter' four times, they would then see the output flushed all in a single line. This makes it very difficult to configure the command. The solution is to call `flush` after every prompt. Since `raw_input` does not have an option to do this, we have to prompt and flush manually. Since we're already accessing stdout directly, it's easier to write to it directly since print adds some formatting that we don't want (namely, a newline at the end of the print). Fixes aws#1925
|
@stramel The fix will be out in the next release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System: Windows 7 64bit
steps to reproduce:
aws configureIt looks as if AWS CLI is thinking it is outputting text however it actually isn't.
The text was updated successfully, but these errors were encountered: