Re: [sr #111211] `pipefail` leak/disablement

function safe_source() { > local saved_opts=$- > local pipefail_on=0 > > # Check if pipefail is set using 'shopt' > if (set -o | grep -q 'pipefail *on'); then > 'on' or 'off' is preceded by a tab character, plus arbitrary padding spaces, so that won't work. But it's a suboptimal a

Re: [sr #111211] `pipefail` leak/disablement

On Mon, Mar 24, 2025 at 03:47:20AM -0400, anonymous wrote: > # Check if pipefail is set using 'shopt' > if (set -o | grep -q 'pipefail *on'); then > pipefail_on=1 > fi To check if an option is set you use [[ -o pipefail ]], not that thing. Also if you run local - in a fun

[sr #111211] `pipefail` leak/disablement

URL: Summary: `pipefail` leak/disablement Group: The GNU Bourne-Again SHell Submitter: None Submitted: Mon 24 Mar 2025 07:47:14 AM UTC Category: None Prior

Re: foo=bar baz=${|...;} cmd segfauls after running ...

On 3/23/25 7:37 PM, Emanuele Torre wrote: If you run a simple command that runs something (not just assignments) and contains an assignment word with ${|;} that is preceeded by at least one other assignment word, bash segfaults. Thanks for the report. The fix was a simple matter of swapping two