ExternalProcess question

Bob, anybody,

Is it safe to launch something as (tersely as) follows:

ExternalProcess new
commandLine:'xyz.exe';
execAsync.

It seems to work (when it works - see below), but I am wondering about
leaks that might result from failing to something??

My goal is create a password-protected launcher for a streamlined shell
(Emerge is the top candidate right now). I also want password-protected
access to explorer, and that is not working yet. AFAICT, #system: is
deprecated because it cannot simultaneously use stdin/out and protect
Dolphin from errantly being closed when the console closes. I can
probably live with that, since I do not need the output in the
situations I envision. Back to ExternalProcess, I suspect that explorer
is loading and closing immediately. Am I missing something silly?

Have a good one,

Bill


--
Wilhelm K. Schwab, Ph.D.
bills@anest4.anest.ufl.edu

Hello all,

> Is it safe to launch something as (tersely as) follows:
>
> ExternalProcess new
> commandLine:'xyz.exe';
> execAsync.
>
> It seems to work (when it works - see below), but I am wondering about
> leaks that might result from failing to something??

I think I got to the bottom of it. My past successes with
ExternalProcess were in cases where the console/window should not be
displayed. Some searching later, I found the SW_HIDE flag, and added a
way to change it to SW_SHOW. Now the explorer and command shell are
visible and appear to work.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
bills@anest4.anest.ufl.edu