[wpkg-users] Execute check and pipes

[Rainer Meier]

Hi Daniel,

Daniel Dehennin wrote:
> In the log I got:
> Execute check for program 'at \| %WPKG%\bin\grep "sc start wpkgservice"' returned '1'. Evaluating condition 'null' revealed false when comparing to expected value of '0'

It looks like the exit value of the expression is 1. I did not test with 
the pipe character yet - so I can't tell you if the WScript exec method 
allows it or not. I might do some tests if I have some time left... hmm, 
not so much at the moment...


> Does it fail because of the "\|" ?

Probably because of the pipe character, but not because of the "\" in 
front of it - see below.


> I don't know if the "\" is only for the log output or if WPKG try to
> run the command as it's shown.

Yes, it is only for the output. WPKG prints each log entry onto one 
single line replacing linefeeds by '|'. This makes the log easier to 
follow/read. Of course if somebody wants to use a log-file browser and 
restore the linefeeds then all pipe symbols within the output would 
become linefeeds as well. So it's a basic principle that special 
characters need to be escaped if they are used without their special 
meaning.

So yes, wpkg.js is just adding the \ in front of the | symbol during log 
file writing, not during execution.

br,
Rainer