Please take a look at this bug

2015-08-23 Thread Mostafa Nazari
I know why this is a bug, but this is! a bug. please inform me if there is any working around this. #!/bin/bash function bug_part() { cat $1 > sample.fisrt cat $1 > sample.second } bug_part *<(echo "TEST")* [ "$(cat sample.fisrt)" != "$(cat sample.second)" ] && echo "THIS IS A BU

Re: Please take a look at this bug

2015-08-23 Thread Ángel González
Mostafa Nazari wrote: > bug_part <(echo "TEST") The <(echo "TEST") construct creates a pipe. You can view it just printing the value that gets passed to the program: $ echo <(echo "TEST") /dev/fd/63 Now, a problem of that pipe is that the contents can only be read once. Indeed, what would the sec

Re: Please take a look at this bug

2015-08-23 Thread John McKown
On Sun, Aug 23, 2015 at 5:42 AM, Mostafa Nazari wrote: > I know why this is a bug, but this is! a bug. please inform me if there is > any working around this. > > #!/bin/bash > > function bug_part() { > cat $1 > sample.fisrt > cat $1 > sample.second > } > > ​​ > bug_part *<(echo "

Re: coredump with wait -n

2015-08-23 Thread isabella parakiss
On 8/22/15, Chris F.A. Johnson wrote: > On Sat, 22 Aug 2015, isabella parakiss wrote: > >> Hi, after running wait -n there's something wrong, ^C doesn't work >> properly anymore: it displays ^C in the readline buffer, but the current >> line stays there until I press enter. Running any command "f