RE: Using the QzshSystem Qshell API

Scott,

Sorry about the name, I pulled it from
your email address. You are right, I
was not opening up stdin, stdout, or
stderr.

One of those things where I assumed that
the file not found message was referring
to touch and not stdin/out/err. I wonder
why the guy who wrote the API couldn't
return the what it was looking for in
the found message.

Your call to QzshCheckShellCommand
will work if you trim the parameters
off of touch. It is still a mystery
to me why ls works and touch does
not since it would seem they both
need to use stdout.

Anyway, thanks for the help,

David Morris

>>> klemscot@klements.com 04/06/02 15:13 PM >>>

On Sat, 6 Apr 2002, David Morris wrote:
>
> Scot,
>
> Thank you for the example, but I still
> get the same error with your code. Going
> back to my original code, it will run ls,
> but won't run something like touch. The
> touch utility does pass the
> QzshCheckShellCommand check. I am trying
> to pass something like:
>
> touch -C 00817 /tmp/test.txt


My name is "Scott" (two Ts),

I'm able to get your 'touch' to work using my example.  When I change
'command' in my example to:

           eval      command = 'touch -C 00817 /tmp/test.txt'

And run the code, the QzshCheckShellCommand will return the errror
'No such path or directory'.  :(

However, if I remove the call to QzshCheckShellCommand, the touch
_does_ work!   If I do a WRKLNK '/tmp/*'  I see a "test.txt".