Good job awk master!
Cheers,
Chris
On Apr 12, 2012, at 6:55 PM, Nguyen, Ricky wrote:
> Worked around my issue by avoiding brackets completely. Used awk regular
> expression instead.
>
> I'd still be interested to know how to do a shell IF statement in PGE
>
> On Apr 12, 2012, at 6:04 PM, Nguy
Hey Ricky,
I think we're running into an envReplace issue here. By default,
it's set to use the '[' as delimeters in CAS-ville for this. Using those
commands in bash will hose the env var replacement.
I guess we could optionally turn off env var replacement in these
scenarios, by putting an attr
Hey Ricky,
The envReplace which is causing this problem is the envReplace applied to the
script... Currently this cannot be turned off... However if you create an issue
for this I will take care of this fix... Updating the XML parser is my next
step in porting wengine changes to trunk cas-pge
Worked around my issue by avoiding brackets completely. Used awk regular
expression instead.
I'd still be interested to know how to do a shell IF statement in PGE
On Apr 12, 2012, at 6:04 PM, Nguyen, Ricky wrote:
> Hi all,
>
> I want to do this in bash:
>
> if [[ $x = 'hello' ]]; then
>
Hi all,
I want to do this in bash:
if [[ $x = 'hello' ]]; then
echo "goodbye"
fi
But if I try that in PGE, it will attempt to do dynamic replacement. So then I
tried this:
if [bash_test]; then
echo "goodbye"
fi
And I still get the same failure. FYI, the script in the work d
