On 20/07/2020 10:52, R.Wieser wrote:
> Ahem,
>
>> I posted a solution - the correct one viz:
>
> It was not about you or Andy.   All three of us wrote the similar thing:
> Check the variables, as one being empty is the likely cause of the problem.
>
> The thing is that Dumas there singled me out.  For what reason ?  He still
> has to tell us..
>
>> OK I didn't explicitly write out the corrected version. Like
>> Andy I prefer to help people think and understand.
>
> The same here.  Why did you think I suggested to print out the GOV and FORCE
> variables ?
>
>>> As for the solution ?   I overthought it.    The problem is that the
>>
>> Twice and still got it wrong!
> ...
>> It might also contain spaces, tabs, newlines etc.
>
> Yeah, that was something I didn't think about ...
>
> And yes, wrapping the environment variable into double quotes does seem to
> do the trick.   Even though my tests in that direction initially failed -
> because I removed the spaces at both sides of the "=".   Didn't realise BASH
> needs them.  Yeah, I'm a rather newbie in regard to Linux  and BASH.  So sue
> me. :-)
>
> Regards,
> Rudy Wieser
>
>
Well I've been around Unix since the '80s and I STILL can't write
complex shell scripts. Its always been quicker to write the thing in C.

--
There’s a mighty big difference between good, sound reasons and reasons
that sound good.

Burton Hillis (William Vaughn, American columnist)

--- SoupGate-Win32 v1.05