Will McGugan

I see. So the error occurs regardless of if you are printing to stdout or not. You didn't include the full traceback btw. The error message would help.

I'm not keen on adding env vars that aren't already a standard. As a library, Rich shouldn't impose its own env vars on to applications. It should be the application...

@joouha I think I need to understand your use case a bit more. Would you be free for a video chat, next week perhaps?

Why not use the prompt to display the digits? Separate lines with `\n`. ```python Prompt.ask('[1] foo\n[2] bar\nPick one') ```

Looks good to me. 👍

Can you elaborate on what this does?

Rich can only capture the stdout / stderr of its own process. If you want your subprocesses to write to the console, you will need to capture the output and...

It's possible. But it's not straightforward. You can capture the output in your `func.py` and send that via a pipe or other IPC mechanism to your main process for printing....

In Jupyter the progress bars are rendered in a different process (the browser) and all output is captured. To do that in your terminal you would essentially have to implement...

This wasn't intentional, and I suspect we should restore the original behaviour. There are differing requirements with respect to capture. Some want the capture output to also go to the...