Provided '-o pipefail' is not specified. 2012/10/14 Andreas Schwab <[email protected]>: > Wladimir Sidorenko <[email protected]> writes: > >> To my mind the '!' operator should have had a higher precedence during >> parsing command line arguments than the pipe and applied only to the >> command it was immediately preceding. So that in >> >> ! command1 | command2 | command3 >> >> it would only negate command1. > > Which doesn't make sense, since the exit code of command1 has no > significance. The exit code of a pipeline is that of the last command. > > Andreas. > > -- > Andreas Schwab, [email protected] > GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 > "And now for something completely different."
- Re: different exit codes in $? and ${PIPESTATUS[@]} Andreas Schwab
- Re: different exit codes in $? and ${PIPESTATUS[@]... Chet Ramey
- Re: different exit codes in $? and ${PIPESTATU... Wladimir Sidorenko
- Re: different exit codes in $? and ${PIPES... Eric Blake
- Re: different exit codes in $? and ${PIPES... Chet Ramey
- Re: different exit codes in $? and ${P... Wladimir Sidorenko
- Re: different exit codes in $? an... Andreas Schwab
- Re: different exit codes in $... Wladimir Sidorenko
- Re: different exit codes ... Chet Ramey
- Re: different exit codes in $? an... Dan Douglas
- Re: different exit codes in $... Chet Ramey
- Re: different exit codes ... Dan Douglas
- Re: different exit codes ... Chet Ramey
- Re: different exit codes in $? an... Chet Ramey
