On 11/20/2015 01:08 PM, Pádraig Brady wrote: > + tee no longer diagnoses write errors to a closed standard output, as this > + can be useful when further piping the output from process substitutions.
I'm not sure this is allowed by POSIX, but at least this regresses for other reasons of EBADF like when the file descriptor is valid but not opened for writing: $ echo | /usr/bin/tee >&0 ; echo $? /usr/bin/tee: standard output: Bad file descriptor /usr/bin/tee: write error 1 $ echo | src/tee >&0 ; echo $? 0 As process substitutions give not that exact control over what happens anyway, I'm 20:80 for adding because the proposed EBADF handling is blurring the situation for all other cases which are relying on exact error diagnostic and exit code. Have a nice day, Berny
