This repository has been archived by the owner on Feb 1, 2022. It is now read-only.
No progress bar output for non-TTY processes #137
Comments
gdman
added a commit
to gdman/cli-ux
that referenced
this issue
Jan 28, 2020
…put when the process is not TTY. The cli-progress library supports no TTY output but it has to be enabled with the noTTYOutput option. The logic is currently - enable no TTY output if the terminal is not dumb and the process is TTY which seems to be the wrong way around. This should be 'enable no TTY output' if the terminal is dumb or the process is not TTY i.e. the terminal is dump or not interactive (i.e. as part of a CI process). (oclif#137)
This was referenced Jan 28, 2020
RasPhilCo
pushed a commit
that referenced
this issue
Apr 15, 2020
The logic is currently - enable no TTY output if the terminal is not dumb and the process is TTY which seems to be the wrong way around. This should be 'enable no TTY output' if the terminal is dumb or the process is not TTY i.e. the terminal is dump or not interactive (i.e. as part of a CI process). (#137)
|
Closed via #138 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The new progress bar feature (PR #131) doesn't show any output when the process is not TTY. The cli-progress library supports no TTY output but it has to be enabled with the noTTYOutput option.
The logic is currently - enable no TTY output if the terminal is not dumb and the process is TTY which seems to be the wrong way around. This should be 'enable no TTY output' if the terminal is dumb or the process is not TTY i.e. the terminal is dumb or not interactive (i.e. as part of a CI process).
The text was updated successfully, but these errors were encountered: