21 Haziran 2021 Pazartesi tarihinde Chet Ramey yazdı:
>
> You're right, and it's not worth changing at this point. It's come up
> before, and the bash interpretation is much more useful and compatible.
Okay then
>
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>
On 6/20/21 4:05 AM, Oğuz wrote:
$ set -o posix
$ uname &>/dev/null
$
`uname &' and `>/dev/null' should be parsed as two separate commands;
that, if I'm not missing anything, is what POSIX says. But bash
doesn't do that in POSIX mode, and redirects both stderr and stdout to
`/dev/n
On Sun, Jun 20, 2021 at 10:18:59AM -0400, Eli Schwartz wrote:
>
> *Neither* behavior is similar to e.g. dash's behavior, or for that
> matter ksh. Both print the uname output after registering it as a
> backgrounded job (redirection does not get applied to the command itself).
Quick comparission
Oğuz writes:
> $ set -o posix
> $ uname &>/dev/null
> $
>
> `uname &' and `>/dev/null' should be parsed as two separate commands;
> that, if I'm not missing anything, is what POSIX says. But bash
> doesn't do that in POSIX mode, and redirects both stderr and stdout to
> `/dev/null'.
A
On 6/20/21 6:30 AM, Chris Elvidge wrote:
> On 20/06/2021 09:05 am, Oğuz wrote:
>> $ set -o posix
>> $ uname &>/dev/null
>> $
>>
>> `uname &' and `>/dev/null' should be parsed as two separate commands;
>> that, if I'm not missing anything, is what POSIX says. But bash
>> doesn't do th
20 Haziran 2021 Pazar tarihinde Chris Elvidge yazdı:
> On 20/06/2021 09:05 am, Oğuz wrote:
>
>> $ set -o posix
>> $ uname &>/dev/null
>> $
>>
>> `uname &' and `>/dev/null' should be parsed as two separate commands;
>> that, if I'm not missing anything, is what POSIX says. But bash
On 20/06/2021 09:05 am, Oğuz wrote:
$ set -o posix
$ uname &>/dev/null
$
`uname &' and `>/dev/null' should be parsed as two separate commands;
that, if I'm not missing anything, is what POSIX says. But bash
doesn't do that in POSIX mode, and redirects both stderr and stdout to
`/d
$ set -o posix
$ uname &>/dev/null
$
`uname &' and `>/dev/null' should be parsed as two separate commands;
that, if I'm not missing anything, is what POSIX says. But bash
doesn't do that in POSIX mode, and redirects both stderr and stdout to
`/dev/null'.
Oğuz
