-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not-TTY #25
Comments
maybe...but generally cli-progress is designed to work in tty environments only - most people don't like a lot of status spam in their logs. if more than 10 people request this feature i will implement it (requires some larger changes..) in the meantime you can simply create a wrapper around cli-progress best regards, Andi |
+1 |
+1. |
it should work in terminal but not in run tasks (see JetBrains Help) |
So do you mean that if I run it from terminal tab then it should work? |
of course - the "Run" tab is not intended to be used as terminal (as JetBrains said...) |
@AndiDittrich |
+1 Other progress bar modules work with WebStorm, and I was hoping to switch to this one. We run a lot of scripts where the progress is useful, and I run them from within the editor. Faster to rerun while coding than to switch to the terminal tab and rerun the command. |
+1 I could really use that feature too, having a render only once a bar is stopped could do the trick |
the feature is comming in v3.1.0 two options will be available to control the behaviour {
// enable output on non tty environments
noTTYOutput: true,
// 10s update interval
notTTYSchedule: 100000
} in noTTY mode, all terminal control sequences will be disabled and the progress bar output will be generated with the given schedule (notTTYSchedule). synchronous updates are not supported |
notty support has been added to the master branch i appreciate your feedback before releasing it |
Can you add some functional to your module to support not-TTY prints?
Maybe setInterval with printing simple percent of completed jobs every 30 sec?
I can't see progress of my jobs from Docker logs...
The text was updated successfully, but these errors were encountered: