Closed
Description
While addressing #1406 and #1398, I've found that the terminal_output
is not mapped to any output when set to 'file'
.
I don't know if this was intended as a feature, but I see it more like an error. Moreover, we have the StdOutCommandLine
that workarounds this behaviour.
What is the rationale behind maintaining these two ways to do the same thing? Would joining them together make sense? Or maybe StdOutCommandLine
should disappear in favor of a CommandLine
that provides one output (currently named out_file
for the StdOutCommandLine
) when terminal_output = 'file'
?
I would implement whatever you see it is the best solution to this issue because it blocks me in finishing the two above-mentioned issues.