On 4/4/24 7:23 PM, Martin D Kealey wrote:
I'm somewhat uneasy about having coprocs inaccessible to each other. I
can foresee reasonable cases where I'd want a coproc to utilize one or
more other coprocs.
In particular, I can see cases where a coproc is written to by one
process, and read fro
On 4/9/24 10:57 AM, Dag-Erling Smørgrav wrote:
Chet Ramey writes:
The fixed version of strtoimax.m4 has been in the devel branch since
October 3, 2022. Since bash-5.2 built fine on FreeBSD 13 before I released
it, I assume the link problem exist only on systems using musl.
des@crash13 ~/src/b
Chet Ramey writes:
> The fixed version of strtoimax.m4 has been in the devel branch since
> October 3, 2022. Since bash-5.2 built fine on FreeBSD 13 before I released
> it, I assume the link problem exist only on systems using musl.
des@crash13 ~/src/bash-5.2% uname -r
On Mon, Apr 8, 2024 at 3:50 PM Chet Ramey wrote:
>
> On 4/4/24 7:23 PM, Martin D Kealey wrote:
> > I'm somewhat uneasy about having coprocs inaccessible to each other.
> > I can foresee reasonable cases where I'd want a coproc to utilize one or
> > more other coprocs.
>
> That's not the intended p
On 4/7/24 8:36 AM, Dag-Erling Smørgrav wrote:
The strtoimax() existence test in m4/strtoimax.m4 has been broken since
its inception in September 2022.
The fixed version of strtoimax.m4 has been in the devel branch since
October 3, 2022. Since bash-5.2 built fine on FreeBSD 13 before I release
On Tue, Apr 09, 2024 at 01:37:08AM +, squeaky wrote:
> Bash Version: 5.2 Patch Level: 21 Release Status: release
>
> Description:
>
> Running
> echo test >& "quote'test"
> should create the file "quote'test", but it creates "quotetest"
> instead.
I can confir
