On 12/21/2015 05:00 PM, 積丹尼 Dan Jacobson wrote:
> OK. Also make sure (info "(coreutils) test invocation") makes it clear that
> one cannot use
> test -f $1 -a $1 ! -ot $2 #and must use
> test -f $1 -a ! $1 -ot $2 #.
Use of -a in test is inherently non-portable. POSIX even says so -
there are
> "EB" == Eric Blake writes:
EB> On 12/21/2015 05:00 PM, 積丹尼 Dan Jacobson wrote:
>> OK. Also make sure (info "(coreutils) test invocation") makes it clear that
>> one cannot use
>> test -f $1 -a $1 ! -ot $2 #and must use
>> test -f $1 -a ! $1 -ot $2 #.
EB> Use of -a in
OK. Also make sure (info "(coreutils) test invocation") makes it clear that
one cannot use
test -f $1 -a $1 ! -ot $2 #and must use
test -f $1 -a ! $1 -ot $2 #.
On 21/12/15 17:18, Dan Jacobson wrote:
> $ man perlop # has a 50 line section called
>Operator Precedence and Associativity
>
> Might (info "(coreutils) test invocation") not fully specify test's?
> Might (info "(coreutils) expr invocation") not fully specify expr's?
expr precedence is quite
On 22/12/15 00:21, 積丹尼 Dan Jacobson wrote:
>> "EB" == Eric Blake writes:
>
> EB> On 12/21/2015 05:00 PM, 積丹尼 Dan Jacobson wrote:
>>> OK. Also make sure (info "(coreutils) test invocation") makes it clear that
>>> one cannot use
>>> test -f $1 -a $1 ! -ot $2 #and must use
> "PB" == Pádraig Brady writes:
PB> +Also @samp{!} is a shell special character and needs to be quoted.
Perhaps say instead:
Also @samp{!} is often a shell special character and is best used quoted.
$ man perlop # has a 50 line section called
Operator Precedence and Associativity
Might (info "(coreutils) test invocation") not fully specify test's?
Might (info "(coreutils) expr invocation") not fully specify expr's?