Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: broken pipe message with setopt PRINT_EXIT_VALUE
- X-seq: zsh-workers 48950
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Cc: Samuel Bancal <Samuel.Bancal@xxxxxxx>
- Subject: Re: broken pipe message with setopt PRINT_EXIT_VALUE
- Date: Sat, 29 May 2021 11:43:52 +0000
- Archived-at: <https://zsh.org/workers/48950>
- In-reply-to: <CAH+w=7a+=gPiFVTuAEXo0b04N-vmT4zMxNX0+MeC==-Kxrp8HA@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- References: <b34b34de-dc52-8d24-9b3a-c641bb9bbd79@epfl.ch> <20210528200137.nw35xglpw7j2j4r7@chazelas.org> <CAH+w=7a+=gPiFVTuAEXo0b04N-vmT4zMxNX0+MeC==-Kxrp8HA@mail.gmail.com>
Bart Schaefer wrote on Fri, May 28, 2021 at 14:26:25 -0700:
> You can run the pipeline in a subshell to suppress this behavior:
>
> ( < /dev/urandom tr -dc _A-Z-a-z-0-9 | head -c 32; echo )
>
> PRINT_EXIT_VALUE is disabled in subshells because subshells do not
> normally maintain a jobs table like an interactive shell does.
That's the reason in implementation terms, but what's the reason in
user-facing terms?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author