On 11/11/13 11:48 PM, admn ombres wrote:
> i'm not sure this must be considered as a bug, but using bash 4.2.45
> (end it seems to be the same in the devel branch) the output of :
>
> f1 () { y >& >(z) ; }
> f2 () { y &> >(z) ; }
> declare -f f1 f2
> f1 ()
> {
> x &>>(y)
> }
> f2 ()
> {
>
On 7 November 2013 16:31, Simon Toedt wrote:
> On Thu, Nov 7, 2013 at 3:10 PM, Chet Ramey wrote:
>> On 11/7/13 6:21 AM, Simon Toedt wrote:
>>> On Tue, Nov 5, 2013 at 10:56 PM, Chet Ramey wrote:
>> I'm interested in the patch if cd -@ file works like in ksh. Or
>> whatever, just send the
On 11/7/13 10:31 AM, Simon Toedt wrote:
>> Yes. There are a few issues with the bash-20131025 snapshot. I've
>> attached a patch that fixes them.
>
> Chet, can you push the patch to git to avoid that other people stumble
> over that build issue, please?
I pushed another snapshot this morning.
Currently, an outbound socket connection (client) can be created using the
syntax:
exec 5<> /dev/tcp/HOST/PORT
This patch implements support for accepting incoming connections (server)
using a slightly different syntax:
exec 6<> /dev/tcp/HOST/:PORT # note the colon
The listen/accept call will
Hi Everyone, hi Joel,
the idea is nice, and I can really see that it is useful, but I would
be extremely careful with introducing those kind of changes, it can be
easily interpreted as "backdoor feature", that is: from security point
of view it could be a disaster.
cheers,
pg
On Tue, Nov 12,
