Re: BUG??

2016-12-28 Thread Chet Ramey
On 12/28/16 8:09 PM, Peter & Kelly Passchier wrote: > Is this a bug? These both output "q=1" > > q=1 > [[ ((q==1)) ]] && echo q=1 > > q=0 > [[ ((q==1)) ]] && echo q=1 > No. These both end up checking whether the length of the string "q==1" is non-zero, which it is. -- ``The lyf so short, the

Re: BUG??

2016-12-28 Thread Charles Daffern
On 29/12/16 01:09, Peter & Kelly Passchier wrote: > Is this a bug? These both output "q=1" > > q=1 > [[ ((q==1)) ]] && echo q=1 > > q=0 > [[ ((q==1)) ]] && echo q=1 > > This looks like an incorrect use of [[/((. The correct phrasing would be: q=1 ((q==1)) && echo q=1 q=0 ((q==1)) && echo q=1

BUG??

2016-12-28 Thread Peter & Kelly Passchier
Is this a bug? These both output "q=1" q=1 [[ ((q==1)) ]] && echo q=1 q=0 [[ ((q==1)) ]] && echo q=1

Re: command_not_found_handle and sourced script

2016-12-28 Thread Dominique Ramaekers
Op 27-12-16 om 00:23 schreef Dan Douglas: > On Mon, Dec 26, 2016 at 12:42 PM, Dominique Ramaekers > wrote: >> As I understand it, the command_not_found_handle is not triggered on an >> unknown command in a shell script, run normally. > Where'd you here that? That's easy to test. > > $ bash <<<'c