Re: test for "command not found" before expanding shell parameters

2014-04-22 Thread Alan Young
On Mon, Apr 21, 2014 at 3:16 AM, Andreas Schwab wrote: > And if $greo is null the condition will also be true. Really? I'll be damned. That explains this problem I've been having. -- Alan Young

Re: test for "command not found" before expanding shell parameters

2014-04-20 Thread Alan Young
; message: > > "bash: greo: command not found" > > /me wonders if it is mandatory first to expand the complete command line > before realizing that the command isnÄt ther ? > > -- > Toralf > > -- Alan Young

Re: test for "command not found" before expanding shell parameters

2014-04-20 Thread Alan Young
No, because the $greo semanti /var/db/pkg/*/*/USE line will not be executed at all. The if [ -n $greo ] condition only passes if $greo contains the path of the greo application. On Sun, Apr 20, 2014 at 12:05 PM, Toralf Förster wrote: > On 04/20/2014 07:58 PM, Alan Young wrote: >> greo=