Re: Failed $(

2023-04-03 Thread Emanuele Torre
On Mon, Apr 03, 2023 at 10:30:29AM -0400, Chet Ramey wrote: > On 3/31/23 10:20 PM, Zev Weiss wrote: > > > Bash Version: 5.2 > > Patch Level: !PATCHLEVEL! > > Release Status: release > > > > Description: > > > > When 'set -e' is enabled, file-content substitutions of the form $(<...) > > cause an

Re: Failed $(

2023-04-03 Thread Chet Ramey
On 3/31/23 10:20 PM, Zev Weiss wrote: Bash Version: 5.2 Patch Level: !PATCHLEVEL! Release Status: release Description: When 'set -e' is enabled, file-content substitutions of the form $(<...) cause an immediate exit even when the subsitution is in a conditional context such as the condition

Re: Possible problem with ${var%%[...]*}

2023-04-03 Thread Chet Ramey
On 4/2/23 1:28 PM, Robert Elz wrote: Date:Sun, 2 Apr 2023 17:48:24 +0200 From:Martin Schulte Message-ID: <20230402174824.01db4d51fd4f0061fdba7...@schrader-schulte.de> | in the following lines I consider dash's behaviour as correct | an bash's as wrong: All

Re: Possible problem with ${var%%[...]*}

2023-04-03 Thread Chet Ramey
On 4/2/23 12:54 PM, Oğuz wrote: 2 Nisan 2023 Pazar tarihinde Martin Schulte yazdı: Hello, in the following lines I consider dash's behaviour as correct an bash's as wrong: Bash expands `<()' as a process substitution. If you escape `<' or `(' it works fine. I am surprised that `<()' is no