Re: Examples of concurrent coproc usage?

2024-06-11 Thread Zachary Santer
On Mon, Jun 10, 2024 at 1:07 PM Robert Elz wrote: > > The next POSIX will include O_CLOFORK and FD_CLOFORK (or names > similar to those) for open (etc) and fcntl(FDFLAGS)) - that is > analogs of O_CLOEXEC and FD_CLOEXEC but applying to fork() rather > than exec*(). Well there you go. Once people

feature suggestion: ability to expand a set of elements of an array or characters of a scalar, given their indices

2024-06-11 Thread Zachary Santer
Was "bash tries to parse comsub in quoted PE pattern" On Wed, Oct 18, 2023 at 8:19 AM Zachary Santer wrote: > > In Bash 5.2: > $ array=( zero one two three four five six ) > $ printf '%s\n' "${array["{2..6..2}"]}" > two > four > six > $ printf '%s\n' "${array[{2..6..2}]}" > -bash: {2..6..2}: synt

[PATCH] tests: printf: provide explicit TZ start/end

2024-06-11 Thread Grisha Levit
POSIX says about the TZ variable: If the dst field is specified and the rule field is not, it is implementation-defined when the changes to and from DST occur. musl seems to interpret `TZ=EST5EDT` as having DST always in effect, causing the tests that rely on the glibc behavior (of defaul