On 7/5/24 4:38 PM, Emanuele Torre wrote:
More funny things have been discovered since.
It has been brought up when discussing this in the #bash IRC channel of
irc.libera.chat, that if you run eval '
This is a consequence of using the same code for a number of things: the
same function handle
Emanuele Torre writes:
> Yes, clearly that is influencing this new behaviour, but this is new:
> <((
On 7/5/24 2:38 PM, Emanuele Torre wrote:
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's a side effect of making the internal implementations of command and
process
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:
> <(((
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
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
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),
