Bug#735042: [bash] 0 is null (misleading test documentation)

2014-06-22 Thread Filipus Klutiero
Hi Jakub, On 2014-06-20 14:40, Jakub Wilk wrote: [I'm not the maintainer of bash.] * Filipus Klutiero chea...@gmail.com, 2014-01-12, 00:23: According to the part on test of bash's manpage: 1 argument The expression is true if and only if the argument is not null. Yet: $ test 0; echo $? 0

Bug#735042: [bash] 0 is null (misleading test documentation)

2014-06-21 Thread Ivan Shmakov
Jakub Wilk jw...@debian.org writes: * Filipus Klutiero chea...@gmail.com, 2014-01-12, 00:23: [I'm not the maintainer of bash.] [I’m not the one who’s submitted this bug, either.] According to the part on test of bash's manpage: 1 argument The expression is true if and only if

Bug#735042: [bash] 0 is null (misleading test documentation)

2014-06-20 Thread Jakub Wilk
[I'm not the maintainer of bash.] * Filipus Klutiero chea...@gmail.com, 2014-01-12, 00:23: According to the part on test of bash's manpage: 1 argument The expression is true if and only if the argument is not null. Yet: $ test 0; echo $? 0 0 is not null, so the expression is true, so the

Bug#735042: [bash] 0 is null (misleading test documentation)

2014-01-11 Thread Filipus Klutiero
Package: bash Version: 4.3~rc1-1 Severity: minor Tags: upstream X-Debbugs-Cc: bash-...@gnu.org According to the part on test of bash's manpage: 1 argument The expression is true if and only if the argument is not null. Yet: $ test 0; echo $? 0 Given 1 argument, bash interprets the