Re: [Clip] Re: Executing programs in a network unix shell
- One thing I did not see mentioned was the use of the ^!ShellWait
command. This sometimes does a better job than the ^!Wait command. If
you are using a Windows command line to run the Unix shell, this might
I do not have a setup where I can do Unix and Windows together.
Wright, John - Textron Financial wrote:
> Thanks for your suggestions. Your first solution sounds like what I am
> already doing. The second is a bit too complicated for me.
> The work-around I use is this: The clip uses the ^!keyboard keys to kick off
> the program. Following that command, another ^!Keyboard command creates a
> temporary file on the network drive. Even though focus then returns to NTP,
> the second command that creates the file doesn't actually get interperted by
> the shell until the program execution completes. Meanwhile, back in NTP, the
> clip checks for the existance of the file in a loop. When the file is found,
> the clip proceeds.
> It's not pretty, but it works. I was hopeful (but doubtful) that there was
> some simpler way to detect the completion of the program execution.