On Thu, Jul 04, 2024 at 09:08:21PM -0400, Dale R. Worley wrote:
> Emanuele Torre writes:
> > [...]
> > Today, I have noticed that if IFS is set to a value that does not
> > include space, [@]@A will expand to a single value
> > [...]
> > As an aside, [*]@A always expands to the declare command joi
On 6/29/24 10:51 PM, Zachary Santer wrote:
They might already. Now I'm wondering if the documentation just needed updating.
It might, but maybe not how you think. See below.
I'm afraid to report this as a bug, because it feels like something
that running bash in MSYS2 on Windows could be re
Bash 5.2 apparently added <(< file) that expand to the path to a fifo
(openable only for read on BSD) to which the contents of file are
written to, without documenting it.
It also added >(< file) which is rather weird and fun; it expands to
the path to a fifo (openable only for write on BSD),
On 7/2/24 9:59 PM, Zachary Santer wrote:
I *am* seeing a difference between having lastpipe enabled (and job
control off) or not when running your example in the interactive
shell, though:
SECONDS=0; echo $'foo\nbar' | tee >(echo first ; exit 1) >(wc ; sleep
10 ; echo wc) >(tail -n 1; echo tail)
On 7/3/24 8:40 PM, Zachary Santer wrote:
On Wed, Jul 3, 2024 at 11:21 AM Chet Ramey wrote:
Process substitutions are word expansions, with a scope of a single
command, and are not expected to survive their read/write file descriptors
becoming invalid. You shouldn't need to `wait' for them; the
On Fri, Jul 05, 2024 at 15:16:31 -0400, Chet Ramey wrote:
> They're similar, but they're not jobs. They run in the background, but you
> can't use the same set of job control primitives to manipulate them.
> Their scope is expected to be the lifetime of the command they're a part
> of, not run in t
Emanuele Torre writes:
> Bash 5.2 apparently added <(< file) that expand to the path to a fifo
> (openable only for read on BSD) to which the contents of file are
> written to, without documenting it.
I suspect that this is a consequence of
The comâ
mand substitution $(cat
On Fri, Jul 05, 2024 at 04:10:55PM -0400, Dale R. Worley wrote:
> Emanuele Torre writes:
> > Bash 5.2 apparently added <(< file) that expand to the path to a fifo
> > (openable only for read on BSD) to which the contents of file are
> > written to, without documenting it.
>
> I suspect that thi
On Fri, Jul 05, 2024 at 10:38:59PM +0200, Emanuele Torre wrote:
> Yes, clearly that is influencing this new behaviour, but this is new:
> <(((
