Hollywood forums

Hi,

I can capture normal output of command line programs, but the error output is not captured.
This is only possible when redirecting the " *> " output to a file and then read it manually to check if there is new output.

Is there a better way to also capture the stderr output of programs?

Would be nice to specify a option to also capture the stderr (*>) output with the RunOutput event

Actually, this should work already. Which platform did you test this?

I'm on MorphOS and have added support for yt-dlp in ytSearch.
The error output of yt-dlp is not captured.
It's always outputted to a window.

I have workaround it by redirecting stderr (with *>) to a file.
But the (not sooo big) problem is that I only can read from the error output file after yt-dlp finished, because it's locked while it's running.