Rick van Hattem

It's been a long standing issue to add this and it's at the top of my to-do list for this library: - https://github.com/WoLpH/python-progressbar/issues/249 - https://github.com/WoLpH/python-progressbar/issues/189 - https://github.com/WoLpH/python-progressbar/issues/176 It is a...

It's slightly more complicated than that. Within a terminal you can't just write at a specific line, all output is appended at the end of the current line. To rewrite...

While it's not a full solution, this little bit of code reasonably approaches the goal: https://github.com/WoLpH/python-progressbar/issues/189#issuecomment-1246116077

And for a solution that features locks for multithreading: https://github.com/WoLpH/python-progressbar/issues/176

Unfortunately, as far as I am aware, the progressbar can't detect these exceptions since they don't happen in code managed by the progressbar. An alternative that does work properly is...

> I ran with the same problem with stderr and using `progressbar.streams.wrap_stderr`. I did not know that using the progress bar as a context manager would prevent this problem (so...

Nevermind... all that, thanks to your suggestion I found the answer. I can catch [`GeneratorExit`](https://docs.python.org/3/library/exceptions.html#GeneratorExit). Since it doesn't inherit `Exception` I never knew I could catch that from the code....

I've added the two changes to the development branch, can you test if that does everything you were looking for? :) I'm always happy with pull requests if you have...

@mmcewen-g not sure if you noticed the update so pinging you again :) If it works ok I'll create a new release

The issue is that the progressbar is optimized for speed and it doesn't notice a big enough change. By default it will update either: - When the update would be...