Re: Xy-OS/2 shell question

[Robert Holmgren holmgren@xxxxxxxx]

> Reply to note from "R Tennenbaum"  Tue,
> 08 Sep 98 11:34:11 -0500

-> I'm trying to use O2.CMD to start a session of the OS/2 System
-> Editor in the foreground, but I'm a little confused about
-> tweaking the parameters to have it run just as I wish. It
-> should, as seamlessly as possible, call up a particular file
-> within e.exe to the foreground.
->
-> I seem to be close but not quite there; with
->
-> 	O2 e.exe C:\NEWS
->
-> I can get e.exe to come to the foreground, but not without
-> going through a full screen cmd session -- which I can deal
-> with, I guess, except it's a little disorienting and un-seamly,
-> shall we say.

Rafe:

When I run your command, I get a windowed session of E.EXE in the foreground
on the Desktop, and E.EXE is editing file NEWS. That's what I would expect;
that's what you're asking for. What do you expect, or rather want, to happen,
to "have it run just as I wish"?

O2.CMD _is_ still alive, and running in background, if that's what's
disorienting you. But you never see it; it doesn't usually show on the Window
List, so you can't access it; about the only thing
you can do to it is kill it, if SCKILLFEATUREENABLED=1 -- but that would
simply mean that the O2 command shell fails to restore XyWrite as the
foreground application when you terminate E.EXE. A process that you can't see and
can't access and aren't ever aware of seems to me no more disorienting than
HARDERR.EXE or VDOSCTL.EXE or similar detached processes that are always running.

Best,


-----------
Robert Holmgren
holmgren@xxxxxxxx
-----------