Don't consider this as a bash bug. It's a misunderstanding by myself of the pipeline operation.
Maybe a comment should be included in the reference manual to cleary explain that the last command may try to open for writing the file still open for reading by the first command, and that such a situation obviously fails.
Don't consider this as a bash bug. It's a misunderstanding by myself of the pipeline operation.
Maybe a comment should be included in the reference manual to cleary explain that the last command may try to open for writing the file still open for reading by the first command, and that such a situation obviously fails.