[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: no exit status available when a command doesn't exist or fails in pi
From: |
arnold |
Subject: |
Re: no exit status available when a command doesn't exist or fails in pipe to grep |
Date: |
Fri, 10 Sep 2021 01:19:05 -0600 |
User-agent: |
Heirloom mailx 12.5 7/5/10 |
"Neil R. Ormos" <ormos-gnulists17@ormos.org> wrote:
>
> If the piped command's return code were supplied
> in ERRNO instead of as the return value from
> close(), perhaps that would adequately expose the
> required information without contravening the
> earlier-quoted section of the POSIX spec.
It would need to be another variable, not ERRNO, and I don't think it's
worth the trouble of introducing one.
Unfortunately, it's an area of the language that is poorly specified
and likely will remain so. I don't think I'm going to change anything.
Mainly because I doubt that most people use --posix on a regular basis.
Thanks,
Arnold
- Re: no exit status available when a command doesn't exist or fails in pipe to grep, (continued)
- Re: no exit status available when a command doesn't exist or fails in pipe to grep, Neil R. Ormos, 2021/09/09
- Re: no exit status available when a command doesn't exist or fails in pipe to grep, Ed Morton, 2021/09/09
- Re: no exit status available when a command doesn't exist or fails in pipe to grep, Neil R. Ormos, 2021/09/09
- Re: no exit status available when a command doesn't exist or fails in pipe to grep, Ed Morton, 2021/09/09
- Re: no exit status available when a command doesn't exist or fails in pipe to grep, Neil R. Ormos, 2021/09/09
- Re: no exit status available when a command doesn't exist or fails in pipe to grep, Ed Morton, 2021/09/09
- Re: no exit status available when a command doesn't exist or fails in pipe to grep,
arnold <=
- Re: no exit status available when a command doesn't exist or fails in pipe to grep, Ed Morton, 2021/09/10